From: Stan Shebs <shebs@apple.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: Michael Snyder <msnyder@cygnus.com>,
Fernando Nasser <fnasser@redhat.com>,
gdb@sources.redhat.com, vinschen@redhat.com
Subject: Re: Stabs or Dwarf Was: [PATCH]: testsuite/gdb.base/constvars.exp
Date: Wed, 26 Sep 2001 14:39:00 -0000 [thread overview]
Message-ID: <3BB24ABF.1072EE55@apple.com> (raw)
In-Reply-To: <3BB236BB.F50E045E@cygnus.com>
Fernando Nasser wrote:
>
> >From a discussion in gdb-patches
>
> Michael Snyder wrote:
> >
> > (...) we need some kind of test that applies
> > the xfails for stabs and not for dwarf.
> >
>
> There are so many instances where this would be useful that I would
> like to suggest a "gdb_debug_format" procedure to be added to gdb.exp
> that would determine that.
Seems like a good idea to me too.
> We could use a binutils utility on the test file (which we know) and
> parse the output. Does that seem reasonable? Any other suggestions?
I can't think of a completely reliable test on binary files. For
instance, in original a.out, stabs are plain symbols, not in a
distinctly-named section. You also have the problem of an executable
maybe having libraries compiled with stabs, and main prog with dwarf,
and objdump can't distinguish.
On the other, grepping an assembly file produced via -S seems
reliable, since stabs always have at least one ".stabs" line,
and dwarf-2 will always have a .debug_info section mentioned, etc.
All of the compilers that GDB works with have a -S option.
Stan
next prev parent reply other threads:[~2001-09-26 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010925192434.M29024@cygbert.vinschen.de>
[not found] ` <3BB0C224.AB324D56@cygnus.com>
[not found] ` <3BB0CB81.8385E123@redhat.com>
[not found] ` <3BB0F122.3E45B3ED@cygnus.com>
2001-09-26 13:16 ` Fernando Nasser
2001-09-26 14:39 ` Stan Shebs [this message]
2001-09-26 15:02 ` Fernando Nasser
2001-09-26 15:22 ` Elena Zannoni
2001-09-27 5:44 ` Fernando Nasser
2001-09-27 8:24 ` Elena Zannoni
2001-09-26 15:23 ` Michael Snyder
2001-09-27 5:39 ` Fernando Nasser
2001-09-27 12:58 ` Fernando Nasser
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=3BB24ABF.1072EE55@apple.com \
--to=shebs@apple.com \
--cc=fnasser@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@cygnus.com \
--cc=vinschen@redhat.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