Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
To: <gdb@sources.redhat.com>
Subject: Re: Thread signal information
Date: Thu, 25 Jul 2002 08:57:00 -0000	[thread overview]
Message-ID: <001f01ea907b$e385b7f0$9a0a0109@zhangl> (raw)
In-Reply-To: <3D3F05C2.8050200@ixiacom.com>

What are inferior function calls?

Lucy
----- Original Message -----
From: "Dan Kegel" <dkegel@ixiacom.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>; <gdb@sources.redhat.com>
Sent: Wednesday, July 24, 2002 12:53 PM
Subject: Re: Thread signal information


> Daniel Jacobowitz wrote:
> >>Does one give up anything by doing a postmortem gdb session
> >>rather than a live session?
> >
> > From a design perspective, in the corefiles we get each thread's
> > registers from the kernel; in live debugging we use thread_db.
> > Given Linux's one-process-one-thread model at present, this has no
> > practical significance.
>
> ... but it might if/when people start using NGPT instead of LinuxThreads.
> I suppose I should check to see what that project plans to do about core
dumps.
>
> > From a convenience perspective, as Andrew said, you lose inferior
> > function calls.  You can't modify memory.  Etc.
>
> Thanks!
> - Dan
>
>


  reply	other threads:[~2002-07-25 15:57 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
2002-07-24 11:57     ` Daniel Jacobowitz
2002-07-24 12:11       ` Dan Kegel
2002-07-25  8:57         ` Lucy Zhang [this message]
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='001f01ea907b$e385b7f0$9a0a0109@zhangl' \
    --to=lucyz@uclink4.berkeley.edu \
    --cc=gdb@sources.redhat.com \
    /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