From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21070 invoked by alias); 21 Jan 2006 18:50:33 -0000 Received: (qmail 21061 invoked by uid 22791); 21 Jan 2006 18:50:32 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 21 Jan 2006 18:50:30 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1F0Noi-0001Gi-G6; Sat, 21 Jan 2006 13:50:28 -0500 Date: Sat, 21 Jan 2006 20:36:00 -0000 From: Daniel Jacobowitz To: Ivan Novick Cc: gdb@sourceware.org Subject: Re: btacktrace on all threads Message-ID: <20060121185028.GA4861@nevyn.them.org> Mail-Followup-To: Ivan Novick , gdb@sourceware.org References: <43D28228.10105@fastmail.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D28228.10105@fastmail.co.uk> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00203.txt.bz2 On Sat, Jan 21, 2006 at 06:49:12PM +0000, Ivan Novick wrote: > Hi, > > Is there an easier way to backtrace all threads in a core file. > > What I am doing now is getting the list of thread numbers manually with > info threads and then going to each thread individually and running > backtrace there. "thread apply all backtrace" -- Daniel Jacobowitz CodeSourcery