From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15756 invoked by alias); 23 Jul 2009 07:00:47 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 15745 invoked by uid 22791); 23 Jul 2009 07:00:46 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20090702223351.64F00404FD@magilla.sf.frob.com> References: <20090702223351.64F00404FD@magilla.sf.frob.com> Date: Thu, 23 Jul 2009 07:00:00 -0000 Message-ID: <8f2776cb0907230000q1b8dc57chc417430fba0f570f@mail.gmail.com> Subject: Re: feature idea: upto From: Jim Blandy To: Roland McGrath Cc: Project Archer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2009-q3/txt/msg00046.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.