From: Eric Paire <paire@ri.silicomp.fr>
To: James Cownie <jcownie@etnus.com>
Cc: "H . J . Lu" <hjl@lucon.org>, 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: Fri, 21 Sep 2001 05:04:00 -0000 [thread overview]
Message-ID: <200109211153.f8LBrww08032@mailhost.ri.silicomp.fr> (raw)
In-Reply-To: <15kMa6-0Je-00@etnus.com>
>
> Eric wrote :-
>
> > There is no support for MT core dumps.
>
> H.J. replied :-
>
> > Try the current Red Hat kernel/ac kernel. They support it. The patch
> > is very small. I am enclosing it here.
>
> However inspection shows that that patch does _not_ implement a
> multi-threaded core dump. What it does is to dump a full core file for
> each thread.
>
> That seems a somewhat perverse approach, given that
>
> 1) the ELF core dump format easily handles a genuine multi-threaded
> core dump (cf Solaris, IRIX, ...)
>
This is not feasible in Linux as Linus does not want to implement any
specific pthread feature in the kernel (and the core dump is 100%
kernel code), e.g. why a thread doing a fault should kill the other,
perhaps the application is written in such a way that it can recover
from it.
> 2) debuggers already know how to read such multi-threaded core dumps
> and present them as a process with multiple threads.
>
The point is that debugger should understand the way MT core dumps are
done
> 3) dumping a full core dump for each thread is (to first
> approximation) using nthreads too much I/O and nthreads too much
> disk space.
>
If you look carefully at it, it only dumps the first thread, and the dump
is no longer allowed for any thread of this process.
> What is wanted is a genuine multi-threaded core dump, not this
> horror...
>
I would not say that it is, because it exists, and we have been leaving
without anything for years. I would just say that it is a first step
that is more useful that nothing.
-Eric
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 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
next prev parent reply other threads:[~2001-09-21 5:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 2:27 James Cownie
2001-09-21 5:04 ` Eric Paire [this message]
2001-09-21 5:25 ` James Cownie
2001-09-21 8:35 ` H . J . Lu
2001-09-21 8:39 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
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-19 0:46 ` 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=200109211153.f8LBrww08032@mailhost.ri.silicomp.fr \
--to=paire@ri.silicomp.fr \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=hjl@lucon.org \
--cc=jcownie@etnus.com \
--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