RE: [ECOS] Trying to Debug Ecos using GDB

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

So you're saying that I won't be able to build an executable that
contains symbol information from the ecos kernel? Just the symbol
information from the application that I created?

In other words the debug symbols from the libtarget.a library will not
get carried over into hello.o during linking?

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 5:00 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:46:21PM -0400, Fahd Abidi wrote:
> 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?

After linking with the application to form an image The debug symbols
will be in place, but just symbols you need. The debug information for
symbols that are not in the image will not be in the image.

There is also no need to strip the image before loading it onto the
target. Your BDI2000 will be able to parse the elf image and download
only what is needed onto the target, ie it won't download the debug
information.

        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