From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11431 invoked by alias); 24 Aug 2005 20:18:44 -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 11308 invoked by uid 22791); 24 Aug 2005 20:18:08 -0000 Received: from hercules.pjmco.ca (HELO pjmco.ca) (65.98.42.122) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 24 Aug 2005 20:18:08 +0000 Received: (qmail 3102 invoked by uid 48); 24 Aug 2005 20:18:06 -0000 Received: from ip-205-174-165-51.Q1Labs.com (ip-205-174-165-51.Q1Labs.com [205.174.165.51]) by webmail.atsresults.com (IMP) with HTTP for ; Wed, 24 Aug 2005 16:18:06 -0400 Message-ID: <1124914686.430cd5fe3f10a@webmail.atsresults.com> Date: Wed, 24 Aug 2005 20:18:00 -0000 From: jo@atsresults.com To: gdb@sources.redhat.com Subject: Can't debug Threaded application MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-SW-Source: 2005-08/txt/msg00095.txt.bz2 Hello Everyone, I believe the problem I am having is the same a bug 848 and 1154. GDB 6.3 can't debug a threaded application. All I get is SIG32s instead of the [NEW THREAD...] message. And when I do a "(gdb)> i thread" I get nothing.... Here are my specs: - Trustix - Linux cobra.q1labs.inc 2.4.30-3trsmp #1 Tue Jun 7 22:56:09 ADT 2005 i686 unknown unknown GNU/Linux - /lib/libc-2.3.2.so GNU C Library stable release version 2.3.2, by Roland McGrath et al. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 3.3.3. Compiled on a Linux 2.4.25-2tr system on 2004-09-29. Available extensions: GNU libio by Per Bothner crypt add-on version 2.1 by Michael Glad and others linuxthreads-0.10 by Xavier Leroy BIND-8.2.3-T5B libthread_db work sponsored by Alpha Processor Inc NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk Report bugs using the `glibcbug' script to . Is there any work arounds for this bug? I have tried this: (gdb)> set auto-solib-add 0 (gdb)> handle S1G32 nostop noprint but this only stops the SIG32 from stopping gdb, I still can't properly debug the program. What do I have to do to get this to work? Thanks Jason