From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3769 invoked by alias); 22 Oct 2003 23:00:36 -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 3761 invoked from network); 22 Oct 2003 23:00:34 -0000 Received: from unknown (HELO lionfish.az05.bull.com) (141.112.4.90) by sources.redhat.com with SMTP; 22 Oct 2003 23:00:34 -0000 Received: from us-phx1.az05.bull.com (us-phx1.az05.bull.com [141.112.40.1]) by lionfish.az05.bull.com (8.12.10/8.12.10) with ESMTP id h9MN0V9i023472 for ; Wed, 22 Oct 2003 16:00:32 -0700 Subject: gdb6.0 and statically linked threaded programs To: gdb@sources.redhat.com Message-ID: From: Todd.Kneisel@Bull.com Date: Wed, 22 Oct 2003 23:00:00 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00253.txt.bz2 I have built gdb6.0 and am having trouble using it to debug a threaded program that is statically linked with the linuxthreads pthread library. Gdb does not detect the creation of threads, it traps signal 32 that the pthread library uses to restart threads, and gets a SIGINT instead of stopping at a breakpoint in a thread. If I dynamically link my program, everything works fine. For a number of reasons, I need to link my program statically. I've begun looking at the gdb code and found the following text in a comment in the thread_db_mourn_inferior function: At present, debugging a statically-linked threaded program is broken, but the check is added below in the event that it is fixed in the future. Is anyone working on fixing this? Or can anyone provide more details about how or why it's broken? Thanks, Todd Kneisel