This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Stabs or Dwarf Was: [PATCH]: testsuite/gdb.base/constvars.exp
- To: Fernando Nasser <fnasser at redhat dot com>
- Subject: Re: Stabs or Dwarf Was: [PATCH]: testsuite/gdb.base/constvars.exp
- From: Michael Snyder <msnyder at cygnus dot com>
- Date: Wed, 26 Sep 2001 15:22:55 -0700
- CC: Stan Shebs <shebs at apple dot com>, Fernando Nasser <fnasser at cygnus dot com>, gdb at sources dot redhat dot com, vinschen at redhat dot com
- Organization: Red Hat
- References: <20010925192434.M29024@cygbert.vinschen.de> <3BB0C224.AB324D56@cygnus.com> <3BB0CB81.8385E123@redhat.com> <3BB0F122.3E45B3ED@cygnus.com> <3BB236BB.F50E045E@cygnus.com> <3BB24ABF.1072EE55@apple.com> <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.