This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] Don't use thread_db on corefiles

On Thu, Dec 13, 2001 at 02:55:31PM -0800, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> > 
> > On Thu, Dec 13, 2001 at 12:21:48PM -0800, Michael Snyder wrote:
> > > Daniel Jacobowitz wrote:
> > > >
> > > > This patch fixes a really frustrating internal error when you open the
> > > > coredump of a multithreaded application.  Depending on your kernel, either
> > > > the core has threads (corefile.c supports this just fine) or it doesn't.
> > > > Neither way will opening libthread_db work right.
> > >
> > > Daniel, what exactly is the problem that you are solving?
> > > What do you mean by "work right"?
> > 
> > Work at all.  Witness:
> What the heck kind of core file is this?  I've never seen
> the behavior you're getting.  GDB certainly works for standard
> corefiles on Linux (which BTW don't have any thread info in them).

This is a multithreaded core file :)

It follows the basic ELF standard for multiple threads in one core
file; multiple PRSTATUS notes, the first of which is the thread that

I'm still putting some touches on the kernel patch itself.  Stopping
multiple threads so you can dump them is a royal pain.

Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]