* gdb.dwarf2 test directory
@ 2004-08-11 17:47 Andrew Cagney
2004-08-11 18:30 ` Michael Chastain
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Cagney @ 2004-08-11 17:47 UTC (permalink / raw)
To: gdb
Hello,
As a sibling to gdb.stabs, should be a gdb.dwarf2 directory? This would
let us directly generate and test specific dwarf2 constructs without
having to rely on a user running a specific version of GCC.
thoughts,
Andrew
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: gdb.dwarf2 test directory
2004-08-11 17:47 gdb.dwarf2 test directory Andrew Cagney
@ 2004-08-11 18:30 ` Michael Chastain
0 siblings, 0 replies; 2+ messages in thread
From: Michael Chastain @ 2004-08-11 18:30 UTC (permalink / raw)
To: gdb, cagney
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-08-11 18:30 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-11 17:47 gdb.dwarf2 test directory Andrew Cagney
2004-08-11 18:30 ` Michael Chastain
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).