From: Michael Snyder <msnyder@cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Stan Shebs <shebs@apple.com>,
Fernando Nasser <fnasser@cygnus.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 15:23:00 -0000 [thread overview]
Message-ID: <3BB2553F.8A639565@cygnus.com> (raw)
In-Reply-To: <3BB24F75.A33E707E@redhat.com>
Fernando Nasser wrote:
>
> Hi Stan,
>
> Thanks for your comments.
>
> Stan Shebs wrote:
> >
> > 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.
> >
>
> True.
>
> I was thinking just in terms of the testsuite. Most test programs are
> a single file. Could we test just the object file for that one?
>
> Another idea: if we can't say t is stabs but we can say it is dwarf,
> we could implement a gdb_is_dwarf instead. Would that help?
The "info source" command will give you that information.
Haven't tried it with AOUT, but it works with stabs/elf and
dwarf/elf. If we got a positive for dwarf we could run the test.
next prev parent reply other threads:[~2001-09-26 15:23 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
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 [this message]
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=3BB2553F.8A639565@cygnus.com \
--to=msnyder@cygnus.com \
--cc=fnasser@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=shebs@apple.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