From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29504 invoked by alias); 6 Nov 2005 18:52:27 -0000 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 Received: (qmail 29494 invoked by uid 22791); 6 Nov 2005 18:52:23 -0000 Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.196) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 06 Nov 2005 18:52:23 +0000 Received: by zproxy.gmail.com with SMTP id v1so178378nzb for ; Sun, 06 Nov 2005 10:52:21 -0800 (PST) Received: by 10.36.55.20 with SMTP id d20mr259109nza; Sun, 06 Nov 2005 10:52:21 -0800 (PST) Received: by 10.36.221.14 with HTTP; Sun, 6 Nov 2005 10:52:21 -0800 (PST) Message-ID: Date: Sun, 06 Nov 2005 18:52:00 -0000 From: B Mullins To: gdb@sourceware.org Subject: Fwd: Thread Debugging - NPTL/PPC Cc: mul.web06@gmail.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-SW-Source: 2005-11/txt/msg00120.txt.bz2 I have two boards, one is a ppc, one is a ppc64. On both boards I have 32 bit libs. Using the exact same libs and binaries on the ppc as the ppc64, gdb on the ppc64 works fine, where as gdb on the ppc fails to track threads. It seems in thread_db_new_objfile, gdb always falls through with TD_NOLIBTHREAD. I've compiled the latest GDB for both boards, my newly compiled version of gdb fails to track threads for both boards. Thus, I now have a functional and a broken gdb for the ppc64. My original intent was to step through gdb on both boards looking for the point of failure. I've compared with LD_DEBUG=3Dfiles for both the broken gdb and the working gdb on the ppc64, the same libs are loaded in both cases. The libc being using in both cases is NPTL enabled. What information could I provide that would allow someone to point me towards the correct place to look for the point of failure? Much Thanks, -Billy