|Debugging newlib library khosla@UDel.Edu (Kapil Khosla) (2002-10-20)|
|Re: Debugging newlib library firstname.lastname@example.org (Ben Elliston) (2002-10-24)|
|From:||"Ben Elliston" <email@example.com>|
|Date:||24 Oct 2002 23:50:36 -0400|
|Organization:||Red Hat Asia-Pacific Pty Ltd|
|Posted-Date:||24 Oct 2002 23:50:36 EDT|
>>>>> "Kapil" == Kapil Khosla <khosla@UDel.Edu> writes:
Kapil> I am working on an embedded sytems project in which I have to
Kapil> port the newlib library to a new architecture.
Kapil> I currently use printf to do my debugging but is there a tool
Kapil> to automate the process.eg If I have to see the flow of
Kapil> fopen(), I want to be able to see that it calls _open_r -->
Kapil> _open in the library.
GDB can do this, but there are a couple of prerequisites. Firstly,
GDB must be ported to your new architecture. Secondly, you would need
a debugging stub running on the hardware of the new architecture -- or
a simulator. You might find the simulator route easier. How are you
executing programs now?
Return to the
Search the comp.compilers archives again.