From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Dwarf2 testsuite
Date: Mon, 11 Oct 2004 03:50:00 -0000 [thread overview]
Message-ID: <416A0309.nail18911G85W@mindspring.com> (raw)
In-Reply-To: <20041008202550.GA4140@nevyn.them.org>
Okay, it works fine in my test bed with:
gdb 6.2.1 and gdb HEAD
gcc 2, gcc 3, gcc 4pre
dwarf-2 and stabs+ (not that it makes any difference)
-feliminate-dwarf2-dups or not (ditto)
drow> I'd prefer to leave the comments now that I've written them, for two
drow> reasons:
drow> (A) !#(*& it, I spent a lot of effort on those comments!
drow> (B) they make it easier to make a copy with only an incremental change
Okay with me.
Two nits:
The copyright notice to Makefile.in. Grab from gdb.fortran/Makefile.in
if you like. (And yeah, the copyright notice in main.c makes me laugh
at my own stubbornness).
Is file2.txt used at all? I could not find a reference to it.
With those things fixed ... approved.
Michael
2004-10-08 Daniel Jacobowitz <dan@debian.org>
* configure.in: Add gdb.dwarf2.
* configure: Regenerated.
* Makefile.in: Add gdb.dwarf2.
* gdb.dwarf2/Makefile.in, gdb.dwarf2/dw2-basic.S,
gdb.dwarf2/dw2-basic.exp, gdb.dwarf2/main.c, gdb.dwarf2/file1.txt,
gdb.dwarf2/file2.txt: New files.
next prev parent reply other threads:[~2004-10-11 3:50 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
2004-10-11 3:50 ` Michael Chastain [this message]
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=416A0309.nail18911G85W@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--cc=gdb-patches@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