From: Mark Kettenis <kettenis@science.uva.nl>
To: "H . J . Lu" <hjl@lucon.org>
Cc: GDB <gdb@sourceware.cygnus.com>
Subject: Re: RFC: Fix gdb 5.1 for Linuxthreads
Date: Wed, 19 Sep 2001 07:06:00 -0000 [thread overview]
Message-ID: <s3iitefqnsw.fsf@soliton.wins.uva.nl> (raw)
In-Reply-To: <20010918152200.A14153@lucon.org>
"H . J . Lu" <hjl@lucon.org> writes:
> This patch seems to work for me. Any comments? It also fixes debugging
> the statically linked linuxthreads binaries.
What's the rationale behind this patch. Even though it might seem to
fix your problems, it looks wrong to me. It seems to add "robustness"
in the wrong places, such that other assumptions that I made in the
lin-lwp.c module might be violated. Certainly the outcome of
is_cloned() won't be correct in some cases.
The problem with attaching should be solved in a different way. And
what's wrong with debugging statically linked LinuxThreads binaries?
Mark
next prev parent reply other threads:[~2001-09-19 7:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 12:47 Is the current gdb 5.1 broken for Linuxthreads? H . J . Lu
[not found] ` <20010917161350.A25349@lucon.org>
2001-09-17 19:13 ` H . J . Lu
2001-09-18 13:56 ` H . J . Lu
2001-09-18 15:22 ` RFC: Fix gdb 5.1 for Linuxthreads H . J . Lu
2001-09-19 5:42 ` Duncan Palmer
2001-09-19 9:19 ` H . J . Lu
2001-09-20 8:21 ` Duncan Palmer
2001-09-19 7:06 ` Mark Kettenis [this message]
2001-09-19 8:58 ` H . J . Lu
2001-09-19 0:46 ` Is the current gdb 5.1 broken for Linuxthreads? Eli Zaretskii
2001-09-19 8:43 ` H . J . Lu
2001-09-19 6:56 ` Mark Kettenis
2001-09-19 7:39 ` Eric Paire
2001-09-19 9:05 ` H . J . Lu
2001-09-20 0:59 ` Eric Paire
2001-09-19 13:39 ` Andrew Cagney
2001-09-20 1:36 ` Eric Paire
2001-09-20 8:03 ` H . J . Lu
2001-09-20 21:49 ` Eric Paire
2001-09-19 9:10 ` H . J . Lu
2001-09-19 6:32 ` Mark Kettenis
2001-09-19 9:16 ` H . J . Lu
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=s3iitefqnsw.fsf@soliton.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=gdb@sourceware.cygnus.com \
--cc=hjl@lucon.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