[Coco] OT: gcc debugging was Re: OS-9 C Compiler

Theodore (Alex) Evans alxevans at concentric.net
Wed Feb 17 10:05:24 EST 2016


On 02/16/2016 07:48 PM, Stephen H. Fischer wrote:
>> Probably not as that kind of integration is generally not the UNIX way.
>
> Ah, the root of the deficiency has been found. Don't ever do anything that would be useful as the years go by.

The idea is to have a collection of small programs that each do one 
thing well.  Of course that is an ideal and many tools do not follow 
this philosophy.

>> external debugger on your code.  There are things like eclipse which
>> will call all of these programs for you and make them appear integrated.
>
> Setting breakpoints at the "C" source level?

You can set breakpoints in gdb.  The easiest way is to set one at a line 
you are currently at.

> When you hit a breakpoint can you then look at your variables in their natural form.
>
> Single step one "C" line at a time?

gdb does this.

> define "watches" so that you can see their variables as they change in real time?

I am unaware of a way to do this, but it is probably possible.

> And more debugging options at the "C" source level?
>
> ----------------------------------
> What about Java?

Eclipse was actually written for Java, but I can't really tell you about 
the debugging facilities as I haven't used then much.



More information about the Coco mailing list