Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: pgilliam@us.ibm.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB paper for GCC summit: New Commands
Date: Sat, 01 Apr 2006 13:21:00 -0000	[thread overview]
Message-ID: <uek0ha0u0.fsf@gnu.org> (raw)
In-Reply-To: <1143681561.21920.426.camel@dufur.beaverton.ibm.com> (message 	from PAUL GILLIAM on Wed, 29 Mar 2006 17:19:21 -0800)

> From: PAUL GILLIAM <pgilliam@us.ibm.com>
> Date: Wed, 29 Mar 2006 17:19:21 -0800
> 
> 1) How do "set|show detach-on-fork" and "set|show follow-fork" work
>    together?

Do you mean "set|show follow-fork-mode"?  If so, the answer is in the
manual (in the node "Processes"); if something there is unclear,
please tell what parts need to be clarified.

>                I think this is the answer:  If 'set detach-on-fork' is
>    off, the 'set follow-fork' works as before.  If 'set detach-on-fork'
>    is on, then the  state of 'set follow-fork' determines which for will
>    be the 'current' fork.  Is this correct?

I think it's the other way around: if detach-on-fork is ON, then "set
follow-fork" behaves as it did before: one of the two processes is
debugged bu GD, while the other runs unimpeded.  If it's OFF, then
both parent and the child are under GDB's control.

Again, I think this is stated quite clearly in the manual, so if
anything there sounds confusing, please identify the confusing parts.

> 2) Does the new fork features also work with vfork?

The text suggests that they do, but I don't know if this is correct as
a matter of fact.

> 3) If the name of the main procedure is 'main', is the start command
> equivalent
>    to 'tbreak main' followed by 'run', or is there something subtle
> going on? 

AFAIK, "start" is equivalent to "tbreak main; run".


  parent reply	other threads:[~2006-04-01 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18 11:13 GDB paper accepted for GCC summit PAUL GILLIAM
2006-03-19 17:05 ` Eli Zaretskii
2006-03-30  0:32 ` PAUL GILLIAM
2006-03-30  1:41   ` Randolph Chung
2006-03-30  4:13     ` Daniel Jacobowitz
2006-03-30 22:42     ` Mark Kettenis
2006-03-30  1:36 ` GDB paper for GCC summit: New Commands PAUL GILLIAM
2006-03-30  4:30   ` Joel Brobecker
2006-04-01 13:21   ` Eli Zaretskii [this message]
2006-04-10 22:27 ` GDB paper at GCC summit: user-level features PAUL GILLIAM
2006-04-11  9:01 ` GDB paper accepted for GCC summit PAUL GILLIAM

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=uek0ha0u0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=pgilliam@us.ibm.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