This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Is the current gdb 5.1 broken for Linuxthreads?
- To: Eric Paire <paire at ri dot silicomp dot fr>
- Subject: Re: Is the current gdb 5.1 broken for Linuxthreads?
- From: "H . J . Lu" <hjl at lucon dot org>
- Date: Fri, 21 Sep 2001 08:35:50 -0700
- Cc: James Cownie <jcownie at etnus dot com>,Andrew Cagney <ac131313 at cygnus dot com>,Mark Kettenis <kettenis at science dot uva dot nl>,GDB <gdb at sourceware dot cygnus dot com>
- References: <15kMa6-0Je-00@etnus.com> <200109211153.f8LBrww08032@mailhost.ri.silicomp.fr>
On Fri, Sep 21, 2001 at 01:53:58PM +0200, Eric Paire wrote:
> >
> > 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.
I am hoping to see POSIX semaphore for Linux. If we want some support
in kernel, kernel may have to know threads. If it is the case, we can
do many other interesting things in kernel for threads.
H.J.