From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9794 invoked by alias); 27 Apr 2009 18:29:21 -0000 Received: (qmail 9785 invoked by uid 22791); 27 Apr 2009 18:29:21 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout6.012.net.il (HELO mtaout6.012.net.il) (84.95.2.16) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 27 Apr 2009 18:29:16 +0000 Received: from conversion-daemon.i-mtaout6.012.net.il by i-mtaout6.012.net.il (HyperSendmail v2007.08) id <0KIR00H00V6LSK00@i-mtaout6.012.net.il> for gdb-patches@sourceware.org; Mon, 27 Apr 2009 21:29:13 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.175.232]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KIR005VMVCOAP90@i-mtaout6.012.net.il>; Mon, 27 Apr 2009 21:29:13 +0300 (IDT) Date: Mon, 27 Apr 2009 18:29:00 -0000 From: Eli Zaretskii Subject: Re: [patch] Do not allow unwinder to terminate inferior in an inferior function call if a C++ exception handler cannot be found. In-reply-to: <49F573A0.4080500@redhat.com> To: Phil Muldoon Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83tz4adk76.fsf@gnu.org> References: <49F17924.50300@redhat.com> <83vdouf8o2.fsf@gnu.org> <49F573A0.4080500@redhat.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00737.txt.bz2 > Date: Mon, 27 Apr 2009 09:58:08 +0100 > From: Phil Muldoon > 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.