From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31835 invoked by alias); 18 May 2006 16:53:51 -0000 Received: (qmail 31824 invoked by uid 22791); 18 May 2006 16:53:49 -0000 X-Spam-Check-By: sourceware.org Received: from intranet.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.6) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 18 May 2006 16:53:48 +0000 Received: (qmail 7076 invoked from network); 18 May 2006 16:53:25 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 May 2006 16:53:25 -0000 To: Andrew STUBBS Cc: Joel Brobecker , PAUL GILLIAM , Daniel Jacobowitz , Mark Kettenis , gdb-patches@sourceware.org Subject: Re: [RFC] Move the frame zero PC check earlier References: <20060510180312.GA12606@nevyn.them.org> <200605130946.k4D9kZ2M001331@elgar.sibelius.xs4all.nl> <20060513151338.GB3721@nevyn.them.org> <200605131642.k4DGgiqa018273@elgar.sibelius.xs4all.nl> <20060516204503.GC13210@nevyn.them.org> <200605162137.k4GLbZiS014187@elgar.sibelius.xs4all.nl> <20060516221837.GA15617@nevyn.them.org> <1147815745.3672.163.camel@dufur.beaverton.ibm.com> <20060517155729.GF27234@adacore.com> <446C3EB3.1040606@st.com> From: Jim Blandy Date: Thu, 18 May 2006 17:36:00 -0000 In-Reply-To: <446C3EB3.1040606@st.com> (Andrew STUBBS's message of "Thu, 18 May 2006 10:30:27 +0100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes 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-05/txt/msg00400.txt.bz2 Andrew STUBBS writes: > Jim Blandy wrote: >> For the record, at the top of this thread I said I thought it was >> fine, too. I've run into these often enough due to deliberate >> attempts by runtimes to terminate the stack that I think it outweighs >> the (minor, to my mind) value of seeing a 0x00000000 frame that >> indicates an actual error. >> GDB should be honest with the user about what it finds, but I don't >> think we can be a multi-platform debugger and be that picky about >> confining each bit of logic to exactly the platforms that promise to >> uphold it. > > How about adding a command: > > set backtrace terminate-on-zero-pc on|off > > and let the user decide. Set it to 'on' by default on the principle > that, if they aren't aware of the possibility, users don't want to see > zero frames they don't understand. > > Just a thought. Well, that would lift the burden of the decision from our shoulders (that is, GDB developers', not restricted to the folks here) to the users'. I think we're probably in a better position to make it.