From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12415 invoked by alias); 20 Jan 2009 20:18:07 -0000 Received: (qmail 12407 invoked by uid 22791); 20 Jan 2009 20:18:06 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-vbr1.xs4all.nl (HELO smtp-vbr1.xs4all.nl) (194.109.24.21) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 20 Jan 2009 20:17:57 +0000 Received: from mail3.aimsys.nl (a80-127-156-242.adsl.xs4all.nl [80.127.156.242]) by smtp-vbr1.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0KKHnCu030041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2009 21:17:50 +0100 (CET) (envelope-from nvbolhuis@aimvalley.nl) Received: from localhost.localdomain (eagle.aimsys.nl [10.10.4.170]) (authenticated bits=0) by mail3.aimsys.nl (8.14.2/8.14.2) with ESMTP id n0KKHgrE015940; Tue, 20 Jan 2009 21:17:45 +0100 Message-ID: <49763169.8070208@aimvalley.nl> Date: Tue, 20 Jan 2009 20:18:00 -0000 From: "N. van Bolhuis" User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Paul Pluzhnikov CC: teawater , gdb@sourceware.org Subject: Re: gdb doesn't show all threads, but gdbserver does References: <4974EBFF.307@aimvalley.nl> <49757D1C.7010309@aimvalley.nl> <8ac60eac0901201037t71b6bd62j8668bd004e933f53@mail.gmail.com> In-Reply-To: <8ac60eac0901201037t71b6bd62j8668bd004e933f53@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2009-01/txt/msg00120.txt.bz2 Paul Pluzhnikov wrote: > On Mon, Jan 19, 2009 at 11:28 PM, Norbert van Bolhuis > wrote: > >> # cat /proc/920/status > > What did you hope to find from status? > proof that 7 threads are really there. > What you really want is /proc/919/maps: this will show whether > libthread_db.so.1 was loaded into gdb, and if so, which one. > > It should be the same as the one which shows up in > 'ldd gdbserver' output. > In fact I did just that. I didn't mention it since it's there (libthread_db.so.1 is loaded into gdb) so this is not the issue.