From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 634 invoked by alias); 8 Mar 2002 03:29:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 491 invoked from network); 8 Mar 2002 03:29:10 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 8 Mar 2002 03:29:10 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 16jB46-0006hv-00; Thu, 07 Mar 2002 22:29:06 -0500 Date: Thu, 07 Mar 2002 19:29:00 -0000 From: Daniel Jacobowitz To: Jeff Jenkins Cc: gdb@sources.redhat.com Subject: Re: GDB & info threads command Message-ID: <20020307222905.A25092@nevyn.them.org> Mail-Followup-To: Jeff Jenkins , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i X-SW-Source: 2002-03/txt/msg00067.txt.bz2 On Thu, Mar 07, 2002 at 07:22:07PM -0800, Jeff Jenkins wrote: > > Hi, > > I have GDB sources from 03/06/02 running on RH7.2 (kernel 2.4.7-10). > I created a multi-threaded app that created 100 threads, and then promptly > dumps core. > (on purpose!) > > I fire up "gdb test core" and do an "info threads" and all I get is one > thread, namely the thread > that caused the SIGSEGV. I was expecting to see the stacks from all 100 > threads. Is there a fix for this? Do I need a newer kernel? > > Any help would be groovey! No Linux kernel currently dumps the thread registers to coredumps. Hopefully I'll get a chance to submit the patches for that in a month or two. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer