From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: More debug info test directories?
Date: Tue, 19 Aug 2003 13:28:00 -0000 [thread overview]
Message-ID: <20030819132837.GA18748@nevyn.them.org> (raw)
In-Reply-To: <3F42250B.7080304@redhat.com>
On Tue, Aug 19, 2003 at 09:24:27AM -0400, Andrew Cagney wrote:
> Hello,
>
> The gdb.stabs directory, while weird :-^, is probably a good unit test.
> What do people think of additional debug info directories vis:
>
> gdb.dw2
> gdb.dw1
>
> (I'm desperate for better names :-) that contain files of raw debug
> info. It would let people test the various readers without needing a
> corresponding compiler.
>
> thoughts?
Absolutely a good idea. What do you think about letting these use the
.inc files in gdb.asm? Writing raw dwarf2 could require arch hooks,
unless you want to point all offsets at constant addresses instead of
at a variable's actual location. For instance some architectures need
to use .word vs .quad.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-19 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 13:24 Andrew Cagney
2003-08-19 13:28 ` Daniel Jacobowitz [this message]
2003-08-28 20:16 ` Andrew Cagney
2003-08-19 17:57 Michael Elizabeth Chastain
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=20030819132837.GA18748@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).