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: delete_breakpoint: don't try to insert other breakpoints


> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 17 Nov 2007 10:42:35 +1300
> Cc: Daniel Jacobowitz <drow@false.org>, vladimir@codesourcery.com,
> 	gdb-patches@sources.redhat.com
> 
>  > > Eli, how is code which will never be reached a feature?
>  > 
>  > The code is never reached only as long as breakpoints are deleted
>  > synchronously (because we remove the breakpoint instruction as soon as
>  > the inferior stops).
> 
> I've run the testsuite using my asynchronous version of GDB, with and
> without Vladimir's change and, in fact, there was one less failure and
> seven more passes with it. Notably, the extra passes with print-threads.exp
> involved breakpoints.

That's because we don't allow deleting breakpoints asynchronously even
in the async version, AFAIK.


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