From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, jimb@redhat.com
Cc: drow@mvista.com
Subject: Re: RFA: Check for corruption of cv_type chain
Date: Fri, 03 May 2002 15:20:00 -0000 [thread overview]
Message-ID: <200205032219.g43MJxL15375@duracef.shout.net> (raw)
! # These tests are intended to catch problems in the STABS reader, so I
! # think it's okay to override the preference the user expressed in
! # their $DEJAGNU file or whatever, and explicitly request extended
! # stabs debugging information. But, if we don't know how to do that,
! # these tests still should pass just fine if the executable uses some
! # other format.
As Daniel J said, please don't do that.
This makes life harder for me. I'd like the tests to be agnostic about
the configurations, and then have the test bed software iterate over
all the interesting configurations.
Suppose that a similar bug started happening with -gdwarf-3, or with a
coff version of gcc (such as Cygwin's gcc), or with the native Solaris
or Irix or HP-UX C++ compiler?
Michael C
next reply other threads:[~2002-05-03 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 15:20 Michael Elizabeth Chastain [this message]
2002-05-03 17:28 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 21:10 Michael Elizabeth Chastain
2002-05-03 19:37 Michael Elizabeth Chastain
2002-05-03 19:20 Michael Elizabeth Chastain
2002-05-03 17:54 Michael Elizabeth Chastain
2002-05-03 18:49 ` Daniel Jacobowitz
2002-05-03 17:33 Michael Elizabeth Chastain
2002-05-03 14:54 Jim Blandy
2002-05-03 15:14 ` Daniel Jacobowitz
2002-05-03 17:10 ` Jim Blandy
2002-05-03 17:25 ` Daniel Jacobowitz
2002-05-03 20:13 ` Jim Blandy
2002-05-03 18:44 ` Michael Snyder
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=200205032219.g43MJxL15375@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb-patches@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