Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Eric Paire <paire@ri.silicomp.fr>
Cc: Mark Kettenis <kettenis@science.uva.nl>, GDB <gdb@sourceware.cygnus.com>
Subject: Re: Is the current gdb 5.1 broken for Linuxthreads?
Date: Wed, 19 Sep 2001 09:05:00 -0000	[thread overview]
Message-ID: <20010919090519.B30455@lucon.org> (raw)
In-Reply-To: <200109191438.f8JEcoR29295@mailhost.ri.silicomp.fr>

On Wed, Sep 19, 2001 at 04:38:51PM +0200, Eric Paire wrote:
> > BTW, debugging threaded apps under Linux will always be somewhat
> > fragile as long as there isn't a sane kernel threads interface to the
> > kernel.  There should be an interface to stop all threads in a
> > synchronous way.  Unfortunately, I have no hope that such an interface
> > will be added to the kernel.
> > 
> I don't agree with you: There are at least 2 bugs in the current Linux
> kernel which makes you think that the support is fragile:
> 1) SIGSTOP management is not-POSIX conformant
> 2) reparenting of debugged processes is buggy
> 

Could you please provide testcases for them? Even better, do you have
kernel patches?

> 
> > > BTW, people may be very disappointed at the current Linuxthreads
> > > support in gdb 5.1.
> > 
> > If they are they should help improving it.  Several people have
> > reported problems.  Most of these I have been unable to reproduce.
> > Hardly anyone even bothers to answer me if I ask for a small
> > self-contained testcase for the problem.
> > 

I provided one small self-contained testcase to show 3 problems:

1. Attach none-first thread doesn't work on dynamic binaries.
2. Attach none-first thread doesn't work on static binaries.
3. Attach first thread doesn't work on static binaries.

Can anyone duplicate them?


H.J.


  reply	other threads:[~2001-09-19  9:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17 12:47 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
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 [this message]
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
2001-09-21  2:27 James Cownie
2001-09-21  5:04 ` Eric Paire
2001-09-21  5:25   ` James Cownie
2001-09-21  8:35   ` H . J . Lu
2001-09-21  8:39   ` Andrew Cagney

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=20010919090519.B30455@lucon.org \
    --to=hjl@lucon.org \
    --cc=gdb@sourceware.cygnus.com \
    --cc=kettenis@science.uva.nl \
    --cc=paire@ri.silicomp.fr \
    /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