Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eric Paire <paire@ri.silicomp.fr>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Andrew Cagney <ac131313@cygnus.com>,
	Mark Kettenis <kettenis@science.uva.nl>,
	GDB <gdb@sourceware.cygnus.com>
Subject: Re: Is the current gdb 5.1 broken for Linuxthreads?
Date: Thu, 20 Sep 2001 21:49:00 -0000	[thread overview]
Message-ID: <200109210448.f8L4mww21688@mailhost.ri.silicomp.fr> (raw)
In-Reply-To: <20010920080356.A18774@lucon.org>

> On Thu, Sep 20, 2001 at 10:36:06AM +0200, Eric Paire wrote:
> > 
> > There is another difficulty on Linux which seems much more important than
> > these ones. There is no support for MT core dumps. As Linus has always
> > refused to add such functionality in the kernel (which is somewhat similar
> > with your simple interface to stop all threads), a solution should be though
> > of in the user space.
> > 
> 
> Try the current Red Hat kernel/ac kernel. They support it. The patch is
> very small. I am enclosing it here.
> 
Thanks, I am aware of this patch that has been flying around for years.
I have never tested it, but I think that as you are able to know where
the faulty thread is (with bt), you should not be able to get a correct
stack trace of other threads (as their register state is not in the dump,
you do not know where to start the stack analysis). Just a guess which
makes me think that this patch is just a first step to a general
multi-threaded dump.

Thanks anyway for the info,
-Eric
P.S. I have always though that there should be a way to get the missing
information in a core dump, but the core dump is gonna be linuxthread-dependent
and not in the standard format of a multithreaded ELF core dump. Unfortunately,
I have not time left to make such investigation...
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Eric PAIRE
Web  : http://www.ri.silicomp.com/~paire  | Groupe SILICOMP - Research Institute
Email: eric.paire@ri.silicomp.com         | 2, avenue de Vignate
Phone: +33 (0) 476 63 48 71               | F-38610 Gieres
Fax  : +33 (0) 476 51 05 32               | FRANCE


  reply	other threads:[~2001-09-20 21:49 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
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 [this message]
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=200109210448.f8L4mww21688@mailhost.ri.silicomp.fr \
    --to=paire@ri.silicomp.fr \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=hjl@lucon.org \
    --cc=kettenis@science.uva.nl \
    /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