From: Simon Richter <Simon.Richter@hogyros.de>
To: loody <miloody@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: how to source level debug if I cannot see source embedded in elf file
Date: Mon, 23 Nov 2009 12:43:00 -0000 [thread overview]
Message-ID: <20091122171617.GL18195@honey.hogyros.de> (raw)
In-Reply-To: <3a665c760911220903y352e7062m2acfd5fb27a1b169@mail.gmail.com>
Hi,
On Mon, Nov 23, 2009 at 01:03:36AM +0800, loody wrote:
> If my tool chain cannot generate elf file without source embedded even
> I compile them with "-g", can I do the source level debugging?
That assembler dump appears to be from a fully linked file, so I'd
suspect the debug info is stripped at link time. Have you passed the -g
option to the link step as well?
Simon
next prev parent reply other threads:[~2009-11-22 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 0:04 loody
2009-11-23 12:43 ` Simon Richter [this message]
2009-11-23 14:31 ` loody
2009-11-24 19:10 ` Dave Korn
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=20091122171617.GL18195@honey.hogyros.de \
--to=simon.richter@hogyros.de \
--cc=gdb@sourceware.org \
--cc=miloody@gmail.com \
/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