This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call

From: Fred Fish <fnf at specifix dot com>
To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
Cc: drow at false dot org, gdb-patches at sourceware dot org
Date: Mon, 13 Feb 2006 11:18:49 -0500
Subject: Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
References: <200602121510.01657.fnf@specifix.com> <200602131047.30428.fnf@specifix.com> <200602131604.k1DG4n9Y025733@elgar.sibelius.xs4all.nl>
Reply-to: fnf at specifix dot com

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

Follow-Ups:
- Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
  - From: Mark Kettenis

References:
- [PATCH] Fix problem with scope.exp test, skipping past init0 call
  - From: Fred Fish
- Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
  - From: Fred Fish
- Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
  - From: Mark Kettenis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]