From: Daniel Jacobowitz <drow@false.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Dwarf2 testsuite
Date: Fri, 08 Oct 2004 20:25:00 -0000 [thread overview]
Message-ID: <20041008202550.GA4140@nevyn.them.org> (raw)
In-Reply-To: <4166EE58.nailDYH15U42R@mindspring.com>
On Fri, Oct 08, 2004 at 03:45:28PM -0400, Michael Chastain wrote:
> Okay, I threw this in my in-queue and I'll reply on Sunday (estimated).
Cool. Thank you.
> Some random comments:
>
> . It's okay to have tests that execute on some systems and not others,
> as long as gnu/hurd and gnu/linux are included. This is actually
> covered in section 6, "platforms to support", in
> http://www.fsf.org/prep/maintain/maintain.html
Hmm, Hurd is ELF also, so that should be fine.
> . Makefile.in needs a copyright notice. Actually all those little
> subdirectories shouldn't even need configure/makefile stuff,
> but I don't wanna get into that right now.
OK.
> . The self-documenting bit is cool, just leave a comment
> "compile the file and run readelf -w to see what is going on".
> In fact you might want to strip the comments from this file,
> because when I go to debug something with a file like this,
> I don't trust the comments in the file anyways.
I'd prefer to leave the comments now that I've written them, for two
reasons:
(A) !#(*& it, I spent a lot of effort on those comments!
(B) they make it easier to make a copy with only an incremental change
> . We definitely need some infrastructure to return what the
> debug format is, but you can just ignore that and do whatever
> for now, as long as it doesn't totally blow up when I explicitly
> test with "runtest /gdb:debug_flags=-gstabs+ -g2".
It won't blow up. In fact, if GDB is working correctly, it will pass -
if it doesn't, that's a bug. Mixed stabs and dwarf2 ought to work.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-08 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 18:35 Daniel Jacobowitz
2004-10-08 19:45 ` Michael Chastain
2004-10-08 20:25 ` Daniel Jacobowitz [this message]
2004-10-11 3:50 ` Michael Chastain
2004-10-12 14:42 ` Daniel Jacobowitz
2004-10-12 14:44 ` Daniel Jacobowitz
2004-10-12 15:54 ` Michael Chastain
2004-10-08 20:38 ` Michael Snyder
2004-10-08 22:16 ` Daniel Jacobowitz
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=20041008202550.GA4140@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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