From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1062 invoked by alias); 22 Aug 2006 20:24:51 -0000 Received: (qmail 944 invoked by uid 22791); 22 Aug 2006 20:24:50 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 Aug 2006 20:24:43 +0000 Received: from elgar.sibelius.xs4all.nl (root@elgar.sibelius.xs4all.nl [192.168.0.2]) by sibelius.xs4all.nl (8.13.4/8.13.4) with ESMTP id k7MKO8Fn021093; Tue, 22 Aug 2006 22:24:08 +0200 (CEST) Received: from elgar.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by elgar.sibelius.xs4all.nl (8.13.6/8.13.6) with ESMTP id k7MKO74L027762; Tue, 22 Aug 2006 22:24:07 +0200 (CEST) Received: (from kettenis@localhost) by elgar.sibelius.xs4all.nl (8.13.6/8.13.6/Submit) id k7MKO79D002013; Tue, 22 Aug 2006 22:24:07 +0200 (CEST) Date: Tue, 22 Aug 2006 20:41:00 -0000 Message-Id: <200608222024.k7MKO79D002013@elgar.sibelius.xs4all.nl> From: Mark Kettenis To: drow@false.org CC: gdb-patches@sourceware.org In-reply-to: <20060820165007.GC20987@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 20 Aug 2006 12:50:07 -0400) Subject: Re: [rfc, frame] Add backtrace stop reasons References: <20060819154646.GA25238@nevyn.them.org> <200608201438.k7KEcJho022644@elgar.sibelius.xs4all.nl> <20060820165007.GC20987@nevyn.them.org> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00165.txt.bz2 > Date: Sun, 20 Aug 2006 12:50:07 -0400 > From: Daniel Jacobowitz > > On Sun, Aug 20, 2006 at 04:38:19PM +0200, Mark Kettenis wrote: > > > Any comments on this patch? It doesn't have any major change on GDB's > > > visible behavior; it changes one error to a printf, but that error was > > > always wrapped in a catch_exceptions anyway, so this is unimportant. > > > The text of the message on a corrupt stack is changed mildly; it says > > > "Backtrace stopped: previous..." rather than just "Previous...". > > > > That's a useful clarification I think. > > Oh, here's another thing which I think is useful: you'll get the > "Backtrace stopped" message every time you say backtrace, but you used > to only get the Previous... error the first time, which I always found > somewhat confusing. That's because we cached the failure, but not the > failure reason. Ouch yes, this is a very good reason to add this functionality.