public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/13011] GDB fails to build against Linux libc's (e.g. musl) without dladdr and libthread_db
Date: Sun, 21 Oct 2012 14:37:00 -0000 [thread overview]
Message-ID: <bug-13011-4717-A6pLjFYoyk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13011-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13011
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> 2012-10-21 14:37:00 UTC ---
It's true that it's a published external interface, but gdb should not use it
without testing for its existence. FYI we now provide dladdr in musl, but I
have not seen any good documentation on how to provide the thread debugging
hooks gdb wants, and it seems highly nontrivial. It would be helpful to have
this fixed, and for gdb to provide some minimal level of thread debugging
support without including half of the debugger in the program being debugged...
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-10-21 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 16:19 [Bug build/13011] New: GDB accesses internals of glibc's dynamic loader, failing to build with alternate libc wkor97gy0eef1fr at p dot mintemail.com
2011-07-31 18:59 ` [Bug build/13011] GDB fails to build against Linux libc's (e.g. musl) without dladdr and libthread_db ppluzhnikov at google dot com
2011-07-31 19:00 ` ppluzhnikov at google dot com
2012-10-21 14:37 ` bugdal at aerifal dot cx [this message]
2015-09-26 5:13 ` xdje42 at gmail 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=bug-13011-4717-A6pLjFYoyk@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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: link
Be 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).