From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24961 invoked by alias); 25 Jan 2007 19:48:49 -0000 Received: (qmail 24953 invoked by uid 22791); 25 Jan 2007 19:48:48 -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; Thu, 25 Jan 2007 19:48:44 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1HAAaO-0005Ml-FE; Thu, 25 Jan 2007 14:48:40 -0500 Date: Thu, 25 Jan 2007 19:48:00 -0000 From: Daniel Jacobowitz To: David Carlton Cc: gdb Subject: Re: multithreaded core files Message-ID: <20070125194840.GA20591@nevyn.them.org> Mail-Followup-To: David Carlton , gdb References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00322.txt.bz2 On Thu, Jan 25, 2007 at 11:40:42AM -0800, David Carlton wrote: > One of my coworkers is looking at a core file from a multithreaded > program. (x86 Linux.) In this situation, GDB only prints a backtrace > from the thread that actually seg faulted; he'd like to see what other > threads were doing at the time. It should already print all the backtraces. If it doesn't, the usual explanation is that you are using a broken kernel version which does not save registers for every thread. Many 2.4 kernels fit that description. -- Daniel Jacobowitz CodeSourcery