Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fred Fish <fnf@specifix.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
Date: Mon, 13 Feb 2006 16:19:00 -0000	[thread overview]
Message-ID: <200602131118.49981.fnf@specifix.com> (raw)
In-Reply-To: <200602131604.k1DG4n9Y025733@elgar.sibelius.xs4all.nl>

On Monday 13 February 2006 11:04, Mark Kettenis wrote:
> Hmm, if you didn't commit the fix yet, can you please hold off doing
> that for a bit?  From your explanation below, it turns out that this
> might have caught a genuine genuine GDB bug.  By "fixing" this we're
> likely not to notice that.

I believe it also causing lots of other testsuite failures as well.
The scope.exp fix was special in that the original test was supposed
to handle needing two successive "next" commands to get past init0,
and that wasn't working.

-Fred


  parent reply	other threads:[~2006-02-13 16:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 20:10 Fred Fish
2006-02-13  6:16 ` Jim Blandy
2006-02-13 15:39 ` Daniel Jacobowitz
2006-02-13 15:47   ` Fred Fish
2006-02-13 15:53     ` Daniel Jacobowitz
2006-02-13 16:05     ` Mark Kettenis
2006-02-13 16:08       ` Daniel Jacobowitz
2006-02-13 16:19       ` Fred Fish [this message]
2006-02-13 16:49         ` Mark Kettenis
2006-02-13 17:47           ` Jim Blandy
2006-02-13 17:54             ` Jim Blandy
2006-02-13 17:57               ` Jim Blandy
2006-02-13 18:08                 ` Mark Kettenis
2006-03-02  0:01             ` Michael Snyder
2006-03-02  6:09               ` Jim Blandy
2006-02-13 18:39           ` Fred Fish

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=200602131118.49981.fnf@specifix.com \
    --to=fnf@specifix.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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