From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/c++testsuite] New test for constructor breakpoints
Date: Tue, 19 Feb 2002 16:04:00 -0000 [thread overview]
Message-ID: <200202200003.g1K03xl32217@duracef.shout.net> (raw)
Aieee, I am having an instant allergic reaction to -notransfer. Nothing
else in the test suite uses it except for some internal multi-line stuff
in gdb_test which I do not trust at all. So we get to be the first
soldier on the beach. I don't want to have result variations depending
on what version of "expect" somebody has.
There's got to be a better way of tracking which breakpoints have
been successfully set. Maybe set_bp_overloaded should record that
information?
Michael C
next reply other threads:[~2002-02-20 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 16:04 Michael Elizabeth Chastain [this message]
2002-02-19 16:12 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-02-18 12:26 Michael Elizabeth Chastain
2002-02-18 13:17 ` Daniel Jacobowitz
2002-02-19 15:35 ` Daniel Jacobowitz
2002-02-16 11:11 Michael Elizabeth Chastain
2002-02-15 16:50 Michael Elizabeth Chastain
2002-02-15 18:28 ` Daniel Jacobowitz
2002-02-14 15:32 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=200202200003.g1K03xl32217@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--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