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: [RFA] Make mi_cmd_break_insert exception-safe.

From: Vladimir Prus <vladimir at codesourcery dot com>
To: "Doug Evans" <dje at google dot com>
Cc: gdb-patches at sources dot redhat dot com
Date: Fri, 1 Feb 2008 19:15:43 +0300
Subject: Re: [RFA] Make mi_cmd_break_insert exception-safe.
References: <200801271715.08542.vladimir@codesourcery.com> <200802011749.42119.vladimir@codesourcery.com> <e394668d0802010745n3e6c1c0fp80b06edbe555a222@mail.gmail.com>

On Friday 01 February 2008 18:45:39 you wrote:
> On Feb 1, 2008 6:49 AM, Vladimir Prus <vladimir@codesourcery.com> wrote:
> >
> > On Friday 01 February 2008 17:24:39 Daniel Jacobowitz wrote:
> > > On Fri, Feb 01, 2008 at 09:53:46AM +0300, Vladimir Prus wrote:
> > > > So, why bother trying to make gdb_breakpoint non-throwing? I believe
> > > > any such change will be at least as complex as making mi_cmd_break_insert
> > > > exception-safe? If your concern is about gdb_ prefix, how about renaming
> > > > gdb_exception into 'set_breakpoint'?
> > >
> > > That's fine too.
> >
> > What about the following, then?
> 
> Heh.  Or rename the function. :-)

Which the patch does, in fact.

- Volodya

References:
- Re: [RFA] Make mi_cmd_break_insert exception-safe.
  - From: Vladimir Prus
- Re: [RFA] Make mi_cmd_break_insert exception-safe.
  - From: Doug Evans

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