From: Andrew Cagney <ac131313@ges.redhat.com>
To: Dan Kegel <dkegel@ixiacom.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
Lucy Zhang <lucyz@uclink4.berkeley.edu>,
gdb@sources.redhat.com
Subject: Re: Thread signal information
Date: Wed, 24 Jul 2002 11:52:00 -0000 [thread overview]
Message-ID: <3D3EF77A.7020304@ges.redhat.com> (raw)
In-Reply-To: <3D3EE3D4.9030502@ixiacom.com>
> Does one give up anything by doing a postmortem gdb session
> rather than a live session? Obviously one loses the ability to continue,
> but what else? Presumably (once we coax the OS into producing the
> proper core dump) we still can do 'info threads' and 'backtrace' on
> each thread, right?
Main thing you loose is inferior function calls. Often they are useful
when it comes to displaying data.
Andrew
next prev parent reply other threads:[~2002-07-24 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 8:58 Lucy Zhang
2002-07-24 9:04 ` Daniel Jacobowitz
2002-07-24 9:47 ` Dan Kegel
2002-07-24 11:52 ` Andrew Cagney [this message]
2002-07-24 11:57 ` Daniel Jacobowitz
2002-07-24 12:11 ` Dan Kegel
2002-07-25 8:57 ` Lucy Zhang
2002-07-25 9:18 ` Daniel Jacobowitz
2002-07-25 18:28 ` how does GDB find the symbols? Lucy Zhang
2002-07-26 10:03 ` 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=3D3EF77A.7020304@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=dkegel@ixiacom.com \
--cc=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