Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/c++testsuite] New test for constructor breakpoints
Date: Tue, 19 Feb 2002 16:12:00 -0000	[thread overview]
Message-ID: <20020219191250.A14958@nevyn.them.org> (raw)
In-Reply-To: <200202200003.g1K03xl32217@duracef.shout.net>

On Tue, Feb 19, 2002 at 06:03:59PM -0600, Michael Elizabeth Chastain wrote:
> 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?

It has been in expect since at least 1995.  I'd much prefer not to have
an allergic reaction to it; in fact I'd much prefer to use it more
universally, to reduce similar cascades.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-02-20  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 16:04 Michael Elizabeth Chastain
2002-02-19 16:12 ` Daniel Jacobowitz [this message]
  -- 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=20020219191250.A14958@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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