From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26769 invoked by alias); 23 Jul 2009 18:15:12 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 26746 invoked by uid 22791); 23 Jul 2009 18:15:10 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Jim Blandy Cc: Project Archer Subject: Re: feature idea: upto In-Reply-To: Jim Blandy's message of Thursday, 23 July 2009 00:00:37 -0700 <8f2776cb0907230000q1b8dc57chc417430fba0f570f@mail.gmail.com> References: <20090702223351.64F00404FD@magilla.sf.frob.com> <8f2776cb0907230000q1b8dc57chc417430fba0f570f@mail.gmail.com> Message-Id: <20090723181434.12C1580560@magilla.sf.frob.com> Date: Thu, 23 Jul 2009 18:15:00 -0000 X-SW-Source: 2009-q3/txt/msg00047.txt.bz2 > For aborts and asserts, I don't think anyone would mind a > default-to-on feature that simply *always* selects the stack frame of > the function containing the abort or assert. And even before a pony, > I'd like to be able to add my own list of > error-printing-functions-that-squawk-and-call-abort that should be > unwound from. .gdbinit already lists some of these. Indeed, my ~/.gdbinit has: define catch crash catch throw b abort b __assert_fail b __assert_perror_fail end But non-nesting "end" parsing means I can't write: define catch crash catch throw comm up end b abort comm up end b __assert_fail comm up end b __assert_perror_fail comm up end end as I would like to. In particular "catch throw" is comically no more useful than "b __cxa_throw" and it would seem most natural for it to do something like the "up" automagically. Thanks, Roland