public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drow at sources dot redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/2696] New: NPTL libthread_db misbehaves at startup of a static executable Date: Wed, 24 May 2006 20:19:00 -0000 [thread overview] Message-ID: <20060524201910.2696.drow@sources.redhat.com> (raw) 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.
next reply other threads:[~2006-05-24 20:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-24 20:19 drow at sources dot redhat dot com [this message] 2006-05-24 20:28 ` [Bug nptl/2696] " roland at gnu dot org 2006-05-24 20:28 ` roland at gnu dot org 2006-06-14 16:25 ` web-sources dot redhat dot com at jankratochvil dot net 2006-10-25 15:03 ` drow at sources dot redhat dot com 2006-10-25 16:03 ` r dot schwebel at pengutronix dot de 2006-10-25 16:03 ` mkl at pengutronix dot de 2006-10-25 18:55 ` roland at gnu dot org 2007-06-27 15:50 ` drow at sources dot redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060524201910.2696.drow@sources.redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).