public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: nbecker@hns.com (Neal D. Becker)
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gcc@gcc.gnu.org
Subject: Re: dependency analyzer vs. drawf
Date: Fri, 11 Oct 2002 07:16:00 -0000	[thread overview]
Message-ID: <x88smzdksgr.fsf@rpppc1.md.hns.com> (raw)
In-Reply-To: <20021011133209.GA30155@nevyn.them.org>

>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:

    Daniel> On Fri, Oct 11, 2002 at 09:24:48AM -0400, Neal D. Becker wrote:
    >> I had previously written a simple python script that would spit out a
    >> list of all source files given an executable (compiled with -g), using
    >> objdump --stabs.
    >> 
    >> Now the default debug format seems to be dwarf (linux, gcc-3.2) and my
    >> script no longer works.  Is there anything equivalent that would work
    >> with the new format?

    Daniel> Oddly, the debug info dumping has moved to readelf.  readelf -wl should
    Daniel> give you enough information.

Thanks.  I can probably make this work, but unfortunately the format
is not very regular so it will be harder to recognize the file names.
Oh well.


  reply	other threads:[~2002-10-11 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11  6:47 Neal D. Becker
2002-10-11  7:07 ` Daniel Jacobowitz
2002-10-11  7:16   ` Neal D. Becker [this message]
2002-10-11  8:10     ` Daniel Jacobowitz

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=x88smzdksgr.fsf@rpppc1.md.hns.com \
    --to=nbecker@hns.com \
    --cc=drow@mvista.com \
    --cc=gcc@gcc.gnu.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).