This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Do not allow unwinder to terminate inferior in an inferior function call if a C++ exception handler cannot be found.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 27 Apr 2009 21:29:17 +0300
- Subject: Re: [patch] Do not allow unwinder to terminate inferior in an inferior function call if a C++ exception handler cannot be found.
- References: <49F17924.50300@redhat.com> <83vdouf8o2.fsf@gnu.org> <49F573A0.4080500@redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 27 Apr 2009 09:58:08 +0100
> From: Phil Muldoon <pmuldoon@redhat.com>
> CC: gdb-patches@sourceware.org
>
> >> +The unwind on terminating exception flag lets the user determine\n\
> >> +what gdb should do if a std::terminate() call is made from the\n\
> >> +default exception handler.\n\
> >> +The default is to unwind the frame."),
> >>
> > This doesn't tell what happens if it's set to OFF.
>
> I actually thought about this, but the off behaviour is just how GDB
> "used to be".
Well, the user who will read that doc string might not know how GDB
"used to be".
> Something like: "If the flag is set to be 'off', GDB
> will allow the inferior to be terminated by the default exception handler."?
Yes, that'd be good. But the first part could be shorter:
If OFF, GDB will allow ...
Thanks.