From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Subject: Re: Problem Compiling gdbserver with musl
Date: Sun, 21 Oct 2012 16:24:52 +0200 [thread overview]
Message-ID: <508405B4.40507@barfooze.de> (raw)
In-Reply-To: <CAPW=hRSk1vcvqXa0=UFuXKHMwG+JNMS1LDYxXRFpbdvmRvi_Xw@mail.gmail.com>
On 10/21/2012 11:19 AM, Brian Wang wrote:
> On Fri, Oct 19, 2012 at 9:54 PM, John Spencer<maillist-musl@barfooze.de> wrote:
>>
>> hello brian, please forward your bug report to gdb mailing list.
>> clearly gdb devs should check if these facilities are available before using
>> them.
>> we must raise awareness of such issues upstream.
> I guess gdb development is somehow tightly coupled with glibc, which
> supplies libthread_db.
> I remember seeing similar issues reported:
> http://sourceware.org/bugzilla/show_bug.cgi?id=13011
>
gdb is supposed to be usable on multiple archs and platforms; but
apparently they think linux == glibc; which is clearly not always the case.
the lwp_info and THREADDB stuff is used unconditionally, even though
they checked for HAVE_THREADDB_H during configure.
it would definitely help if they get your bug report, even if it serves
just a reminder that GNU is not alone out there.
once the critical mass of bug reports is reached, they will finally fix
these issues.
heck, even if they removed the braindead -Werror-by-default, this would
be a big improvement.
next prev parent reply other threads:[~2012-10-21 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 6:13 Brian Wang
2012-10-19 12:30 ` Rich Felker
2012-10-21 9:12 ` Brian Wang
2012-10-19 13:54 ` John Spencer
2012-10-19 14:17 ` John Spencer
2012-10-21 9:19 ` Brian Wang
2012-10-21 14:24 ` John Spencer [this message]
2012-10-21 15:50 ` Brian Wang
2012-10-21 14:32 ` Rich Felker
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=508405B4.40507@barfooze.de \
--to=maillist-musl@barfooze.de \
--cc=musl@lists.openwall.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).