From: Andrew Cagney <cagney@gnu.org>
To: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
Cc: Michael Snyder <msnyder@redhat.com>,
gdb-patches@sources.redhat.com, kettenis@gnu.org
Subject: Re: [rfa] Delete keep_thread_db
Date: Wed, 08 Sep 2004 14:15:00 -0000 [thread overview]
Message-ID: <413F13DD.6070209@gnu.org> (raw)
In-Reply-To: <7318322520085180@weblx058.utsp.utwente.nl>
> Michael Snyder <msnyder@redhat.com> wrote:
>
>
>>> Andrew Cagney wrote:
>>
>>>> > It would appear that, at one stage, this variable had something to do
>>>> > with corefiles, static programs and threads. That's no longer the case
>>>> > so this deletes the stray global.
>>>> >
>>>> > Tested on FC3 with no regressions,
>>>> >
>>>> > Ok?
>>>> > Andrew
>>
>>>
>>> I would have to defer to Mark Kettenis, since he added the
>>> variable, and from the ChangeLogs, seems to be the only one
>>> who's touched it.
>
>
> The code defenitely was there to deal with static binaries. Andrew, how did you come to the conclusion that it is no longer useful? AFAIK there is no static threads test in the testsuite.
I recently added a test case for this feature - staticthreads.exp.
It fails.
> Anyway, I don't care about this code anymore. I've given up on debugging-with threads on Linux. thread-db.c should renamed into linux-thread.c or somesuch. It, and lin-lwp.c have become a mess of workarounds around workarounds around workarounds that probably only work if you run a specific combination of glibc and patched kernel.
>
> So I'm not going to explicitly OK or this patch. Just rely on your own judgement here Andrew.
Andrew
next prev parent reply other threads:[~2004-09-08 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 7:01 M.M. Kettenis
2004-09-08 14:15 ` Andrew Cagney [this message]
2004-09-08 19:45 ` Andrew Cagney
2004-09-08 14:38 ` Daniel Jacobowitz
2004-09-09 17:35 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2004-09-05 16:05 Andrew Cagney
2004-09-07 18:04 ` Michael Snyder
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=413F13DD.6070209@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
--cc=m.m.kettenis@alumnus.utwente.nl \
--cc=msnyder@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: 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