From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31975 invoked by alias); 19 Jan 2009 21:09:28 -0000 Received: (qmail 31967 invoked by uid 22791); 19 Jan 2009 21:09:28 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_20,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-vbr2.xs4all.nl (HELO smtp-vbr2.xs4all.nl) (194.109.24.22) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 19 Jan 2009 21:09:23 +0000 Received: from mail3.aimsys.nl (a80-127-156-242.adsl.xs4all.nl [80.127.156.242]) by smtp-vbr2.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0JL9J7T090072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Jan 2009 22:09:20 +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 n0JL9Ge1022138; Mon, 19 Jan 2009 22:09:16 +0100 Message-ID: <4974EBFF.307@aimvalley.nl> Date: Mon, 19 Jan 2009 21:09:00 -0000 From: "N. van Bolhuis" User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: gdb@sourceware.org Subject: gdb doesn't show all threads, but gdbserver does 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/msg00107.txt.bz2 I built a gdb (v6.8) for powerpc to be executed on powerpc target (This GDB was configured as "powerpc-e300c3-linux"...). If I use this target gdb to debug my powerpc program and hit a breakpoint "info threads" shows only one thread. This is incorrect since there are 7 threads (cat /proc//status shows 7 threads). If I debug the same program using gdbserver on target and gdb on a host=i686 (This GDB was configured as "--host=i686-linux --target=powerpc-e300c3-linux"...) "info threads" shows the expected 7 threads. How can this be ? (I noticed the target gdbserver needs libthread_db.so.1, the target gdb does not. Maybe this is what's causing this).