From: Daniel Jacobowitz <drow@mvista.com>
To: Lucy Zhang <lucyz@uclink4.berkeley.edu>
Cc: gdb@sources.redhat.com
Subject: Re: multi-thread debugging not working
Date: Tue, 16 Jul 2002 19:08:00 -0000 [thread overview]
Message-ID: <20020717020816.GA9288@nevyn.them.org> (raw)
In-Reply-To: <005501ea89be$3a5b1260$9a0a0109@zhangl>
On Tue, Jul 16, 2002 at 07:07:09PM -0700, Lucy Zhang wrote:
>
> ----- Original Message -----
> From: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
> To: "Dan Kegel" <dkegel@ixiacom.com>; <gdb@source.redhat.com>
> Sent: Friday, July 16, 2038 7:05 PM
> Subject: Re: multi-thread debugging not working
>
>
> > Really?
> > I'm running on Linux Redhat
> > Version 2.2
> > Machine i686
> >
> > the core dump is converted and has the VMA's for the thread stacks. GDB
> > still won't see it?
It has the VMA for every stack. It doesn't have their registers,
however.
> >
> > ----- Original Message -----
> > From: "Dan Kegel" <dkegel@ixiacom.com>
> > To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
> > Sent: Tuesday, July 16, 2002 6:10 PM
> > Subject: Re: multi-thread debugging not working
> >
> >
> > > What operating system? Linux by default doesn't do multithreaded core
> > dumps.
> > >
> >
>
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-17 2:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 19:05 Lucy Zhang
2002-07-16 19:08 ` Daniel Jacobowitz [this message]
2002-07-17 12:54 ` Lucy Zhang
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 13:16 problem loading libpthread.so Lucy Zhang
2002-07-16 13:23 ` Daniel Jacobowitz
2002-07-16 16:54 ` multi-thread debugging not working Lucy Zhang
2002-07-16 18:41 ` Daniel Jacobowitz
2002-07-17 15:08 ` Jim Blandy
2002-07-17 16:30 ` Lucy Zhang
2002-07-18 14:55 ` Jim Blandy
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=20020717020816.GA9288@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=lucyz@uclink4.berkeley.edu \
/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