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

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".

I am a newbie to ecos so maybe I am not clear on how to get to opening
and viewing the kernel and its code in GDB. Any tips and assistance
would be greatly appreciated.

Fahd
 

--
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 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 17:33 Fahd Abidi [this message]
2006-04-12 18:17 ` oli
2006-04-12 18:49 ` Andrew Lunn
2006-04-12 20:18 Fahd Abidi
2006-04-12 20:20 ` Andrew Lunn
2006-04-12 20:40 Fahd Abidi
2006-04-12 20:45 ` Andrew Lunn
2006-04-12 20:59 Fahd Abidi
2006-04-12 21:11 ` 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=81C69D96BDD30640952C7A404004AA2543A59E@ultsol01.tewks.ultsol.local \
    --to=fabidi@ultsol.com \
    --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).