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], "kerravon86" <kerravon86@...> wrote:
>
> --- In [email protected], "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.
>