From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, gdb@sources.redhat.com
Cc: ezannoni@redhat.com, fnasser@redhat.com, jimb@redhat.com
Subject: Re: [rfc] plans for linespec.c
Date: Wed, 08 Jan 2003 00:12:00 -0000 [thread overview]
Message-ID: <200301080012.h080CdS01449@duracef.shout.net> (raw)
Hi David,
Would it be reasonable for you to double your testing and test
stabs+ as well as dwarf-2?
I'm not worried about gcc 2.95.3, gcc HEAD, and so on, because eventually
my dragnet catches that stuff and I feed it back. But there are enough
differences between dwarf-2 and stabs+ that I would be more comfortable
if you tested with both before committing symbol-manipulation patches.
Other than that, I'm all for your plan of attack on decode_line_1.
Michael C
next reply other threads:[~2003-01-08 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 0:12 Michael Elizabeth Chastain [this message]
2003-01-08 23:22 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 16:09 Michael Elizabeth Chastain
2003-01-09 4:24 Michael Elizabeth Chastain
2003-01-09 6:01 ` David Carlton
2003-01-09 9:45 ` Joel Brobecker
2003-01-07 22:22 David Carlton
2003-01-08 14:25 ` Elena Zannoni
2003-01-08 22:48 ` David Carlton
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=200301080012.h080CdS01449@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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