This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb.dwarf2 test directory
- From: Michael Chastain <mec dot gnu at mindspring dot com>
- To: gdb at sources dot redhat dot com, cagney at gnu dot org
- Date: Wed, 11 Aug 2004 14:30:26 -0400
- Subject: Re: gdb.dwarf2 test directory
- References: <411A5BBA.1020508@gnu.org>
Andrew Cagney <cagney@gnu.org> wrote:
ac> As a sibling to gdb.stabs, should be a gdb.dwarf2 directory?
Sounds good to me.
I haven't been in gdb.stabs for a while but it's full of strange stuff,
like 'sed' scripts that run on the host machine (not the build machine).
I don't want that weird stuff copied blindly into gdb.dwarf2.
gdb.dwarf2 is a fine name.
Most of the test suite, even gdb.asm, accepts "runtest --target_board
unix/gdb:debug_flags=-gdwarf-2" or "...=-gstabs+" to specify the debug
format. Think about how that interacts with an explicit dwarf-2
directory. Off the top of my head, I think it would be fine to say: "if
the debug_flags includes -gstabs\[+\], then just skip these tests".
We've been stumbling through this issue with asm-source.exp.
ac> This would let us directly generate and test specific dwarf2 constructs
ac> without having to rely on a user running a specific version of GCC.
Yes. That's the right way to test!
Michael C