Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: jjohnstn <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Ugly thread step situation
Date: Tue, 14 Sep 2004 22:42:00 -0000	[thread overview]
Message-ID: <4147734F.50009@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0409141729550.8039-200000@tooth.toronto.redhat.com>

> Anyway, if the consensus is that the patch is helpful in the short-term, I 
> am more than happy to check it in.

What's involved in adding some sort of testcase?

If this were committed, the testcase will act as our insturance ensuring 
that the s/short/long/ term fix, or even an unrelated change, do not 
re-inroduce this bug.  Even without this, the testcase acts as a 
red-flag identifying a breakage that any long term fix needs to handle.

Andrew



  reply	other threads:[~2004-09-14 22:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 21:44 jjohnstn
2004-09-14 22:42 ` Andrew Cagney [this message]
2004-09-14 23:25 ` Daniel Jacobowitz
2004-09-15 17:36   ` Jeff Johnston
2004-09-15 17:53     ` Andrew Cagney
2004-09-15 17:59       ` Jeff Johnston
2004-09-15 18:21     ` 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=4147734F.50009@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@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