From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12845 invoked by alias); 24 May 2006 20:19:17 -0000 Received: (qmail 12824 invoked by uid 48); 24 May 2006 20:19:11 -0000 Date: Wed, 24 May 2006 20:19:00 -0000 From: "drow at sources dot redhat dot com" To: glibc-bugs@sources.redhat.com Message-ID: <20060524201910.2696.drow@sources.redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug nptl/2696] New: NPTL libthread_db misbehaves at startup of a static executable X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00151.txt.bz2 List-Id: In short, there is no way to either enable libthread_db at _start time for a static binary, or find the appropriate time to initialize it later. I propose allowing it to initialize, and then reporting the "creation" of the first thread once the pthreads library is initialized. The patch is here: http://sourceware.org/ml/libc-alpha/2006-03/msg00014.html Without a fix for this problem, GDB can not debug static executables which use NPTL. -- Summary: NPTL libthread_db misbehaves at startup of a static executable Product: glibc Version: 2.4 Status: NEW Severity: normal Priority: P2 Component: nptl AssignedTo: drepper at redhat dot com ReportedBy: drow at sources dot redhat dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=2696 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.