From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7603 invoked by alias); 2 Mar 2006 17:38:53 -0000 Received: (qmail 7595 invoked by uid 22791); 2 Mar 2006 17:38:52 -0000 X-Spam-Check-By: sourceware.org Received: from xproxy.gmail.com (HELO xproxy.gmail.com) (66.249.82.201) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 02 Mar 2006 17:38:50 +0000 Received: by xproxy.gmail.com with SMTP id s15so303415wxc for ; Thu, 02 Mar 2006 09:38:48 -0800 (PST) Received: by 10.70.117.4 with SMTP id p4mr3592927wxc; Thu, 02 Mar 2006 09:38:48 -0800 (PST) Received: by 10.70.125.17 with HTTP; Thu, 2 Mar 2006 09:38:48 -0800 (PST) Message-ID: <8f2776cb0603020938s3d43f8cx38b79fba44c87a70@mail.gmail.com> Date: Thu, 02 Mar 2006 17:38:00 -0000 From: "Jim Blandy" To: "Andrew STUBBS" Subject: Re: Suggestion: backtrace stop guard for threads callstacks Cc: "Joel Brobecker" , gdb-patches@sources.redhat.com In-Reply-To: <4406CEB2.5000802@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060302012943.GK1579@adacore.com> <20060302031921.GA24107@nevyn.them.org> <4406CEB2.5000802@st.com> 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-03/txt/msg00051.txt.bz2 On 3/2/06, Andrew STUBBS wrote: > How about: > > set backtrace main-functions main;mytaskfunc;_start > > or perhaps: > > set backtrace add-main-function mytaskfunc > > so that the user can stop backtraces whereever is appropriate for their > environment. That's certainly easy to do. But it's clearly preferable for people to properly mark their thread start functions. If I'm remembering right, we haven't yet seen any reports of this problem in cases where we couldn't get the thread start function marked. So I'd argue we don't have any situations where this command was needed --- only cases where using it would have helped people paper over an underlying problem that needs to be fixed elsewhere. Given how often this comes up, would it make sense to add an appendix to the GDB manual explaining how to terminate backtraces?