public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Fahd Abidi" <fabidi@ultsol.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Trying to Debug Ecos using GDB
Date: Wed, 12 Apr 2006 20:18:00 -0000	[thread overview]
Message-ID: <81C69D96BDD30640952C7A404004AA2543A5A5@ultsol01.tewks.ultsol.local> (raw)

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?

The resulting executable is only 2mb in size, the library with symbols
was 17mb, so obviously during the linking process all the debug symbols
got removed from the ecos kernel.

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 3: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 01:39:24PM -0400, Fahd Abidi wrote:
> Hello,
> 
> I am using a BDI2000 JTAG emulator and am trying to debug the ecos 
> kernel at its startup and low level functions. I am getting stuck and 
> a very early point In the process, the Kernel Builds fine using the 
> cygwin based tools I got from ecos.sourceware.org and I have a 
> libtarget.a file created that has debug symbols in it. However I have 
> been unable to read the debug symbols from the file into gdb.
> 
> Using objdup -g to display the debug info says that the .o files 
> included have no recognized debugging info.
> 
> However using objdump-S shows that I do have source code intermixed 
> with the disassembly so it does find source code and hence must have 
> the debug info built in.
> 
> Using objcopy to strip the debug symbols takes the 16mb libtarget.a 
> file to 1.7mb so I am convinced the debug symbols are in the file.
> 
> If I try and open libtarget.a with GDB6.3&4 I get an error saying 
> "error not in executable format".

This is correct. libtarget.a is a library, not an application. 

You need to link the library to your application to form a complete
system image. Then boot that image.

        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

             reply	other threads:[~2006-04-12 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 20:18 Fahd Abidi [this message]
2006-04-12 20:20 ` Andrew Lunn
2006-04-12 21:54   ` [ECOS] " Grant Edwards
  -- strict thread matches above, loose matches on Subject: below --
2006-04-12 20:59 [ECOS] " Fahd Abidi
2006-04-12 21:11 ` Andrew Lunn
2006-04-12 20:40 Fahd Abidi
2006-04-12 20:45 ` Andrew Lunn
2006-04-12 17:33 Fahd Abidi
2006-04-12 18:17 ` oli
2006-04-12 18:49 ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81C69D96BDD30640952C7A404004AA2543A5A5@ultsol01.tewks.ultsol.local \
    --to=fabidi@ultsol.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).