RE: Re: fullscreen debugger

Does it stop anywhere? or similar to CEDF - just at the KICKS calls. 
 
Do you have a method for single stepping? or similar to CEDF?
 
I am thinking about that part - Want to be able to set breakpoints anywhere
and single step and then examine etc
 
 
Also need to start the program from the debugger - In CICS I guess you can
trap the transaction initiation
IBM DEBUG uses the LE interface to start the debugging session
I guess that the best way for me to go is to start the program from the
debugging session.
thoughts anyone?
 
Roc


  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
mfnoel
Sent: Tuesday, August 17, 2010 17:14 
To: [email protected]
Subject: [H390-VM] Re: fullscreen debugger


  

The full screen debugger I have working for KICKS ("December" release?) is
for Cobol. It works by having the KICKS preprocessor generate line number
calls for KEDF (the normal KICKS debugger), then KEDF uses the line number
to call up a screenful of source that the preprocessor/compile proc wrote to
a vsam file. Working well as a source trace, but no other functionality, no
doc and clumsy compile procedure will prevent its release before "December".
Assuming I shortly get the other KICKS/GCC issues resolved I may have source
debug working for GCC as well by "December".

--- In [email protected] <mailto:H390-VM%40yahoogroups.com> ,
"kerravon86" <kerravon86@...> wrote:
>
> --- In [email protected] <mailto:H390-VM%40yahoogroups.com> ,
"Rocky" <rocsystems@> wrote:
> > 
> > Next project is a full screen debugger for VM/370 
> > - Just thinking about that now - any ideas are welcome.
> 
> Well one thing that would be good is for it to
> also debug C code. GCC has the ability to
> intersperse the assembler output with C source
> line numbers.
> 
> So it would be good if you wrote with the idea
> that the source language may not be assembler,
> even if you "only" support assembler to start
> with.
> 
> Note - I don't tend to debug using a debugger
> myself. Nor do I write much code on VM
> specifically. It's just a general suggestion.
> 
> BFN. Paul.
>