RE: [ECOS] Trying to Debug Ecos using GDB

["Fahd Abidi" <fabidi@ultsol.com>]

I'm trying to create a test case where I will use a BDI2000 JTAG
emulator to debug the ecos kernel, for that I need an image that has all
the symbols built in. I will then strip the executable to create an
image that does not have any debug symbols to load onto the target, that
way I can debug the kernel thru a JTAG probe. The larger image with
debug symbols is used only on the host GDB and the stipped executable
sits on the target.

Is this possible? Is there any way to tell the linker to leave the debug
symbols in place?

Thanks,

Fahd
 


-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: Wednesday, April 12, 2006 4:30 PM
To: Fahd Abidi
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Trying to Debug Ecos using GDB


On Wed, Apr 12, 2006 at 04:23:48PM -0400, Fahd Abidi wrote:
> Thank you very much for that tip. I used an example hello world 
> application and linked it to ecos and have an executable image that 
> can be opened with GDB.
> 
> But now it seems like the executable image only has the symbols built 
> in for my hello.c program and no other kernel source files are 
> present. How can I build the application + library so that debug 
> information for the entire kernel is also present?

Why would you want to do that? 

eCos is designed for embedded systems where memory is short. So linking
to the application leaves out everything that is not used.

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss




--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss