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: Jim Blandy <jimb at red-bean dot com>
To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
Cc: fnf at specifix dot com, drow at false dot org, gdb-patches at sourceware dot org
Date: Mon, 13 Feb 2006 09:47:05 -0800
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> <200602131118.49981.fnf@specifix.com> <200602131648.k1DGmUqx009322@elgar.sibelius.xs4all.nl>

Actually, having seen other's responses here, I'm inclined to say that
the proper fix is to simply drop the code in scope.exp for getting
from the opening brace to the first line.  Setting a breakpoint on
main simply shouldn't leave you on the opening brace, and that test
suite logic has always been papering over a bug.

If prologues contain calls to __main, then the prologue analyzers
should skip them.

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

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
- 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]