From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: gdb@sources.redhat.com
Subject: GDB paper for GCC summit: New Commands
Date: Thu, 30 Mar 2006 01:36:00 -0000 [thread overview]
Message-ID: <1143681561.21920.426.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <1142633147.21920.400.camel@dufur.beaverton.ibm.com>
Here is stuff about new commands I gleaned from NEWS. I have some
questions at the end and would welcome any comments. (I intend to do
new features separately from new commands and I know there will be some
overlap).
Feature: Checkpoints
commands:
checkpoint
restart <n>
info checkpoints
delete-checkpoint <n>
Feature: fork
commands:
set|show detach-on-fork
info forks
fork <n>
delete-fork <n>
detach-fork <n>
Feature: Convenience variables
commands:
init-if-undefined
Feature: displaying arrays
command:
set print array-indexes
Feature: logging output to a file
command:
set|show logging
Other New Commands:
start
maint set profile on|off
disconnect
Removed Commands:
removed replacement
set|show arm dissembly-favor set|show arm disassembler
othernames set arm disassembler
set|show remotedebug set|show debug remote
set|show archdebug set|show debug arch
set|show eventdebug set|show debug event
regs info registers
set prompt-escape-char - none -
Qustions:
1) How do "set|show detach-on-fork" and "set|show follow-fork" work
together? 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?
2) Does the new fork features also work with vfork? If not, they are
inconsistent with 'set|show follow-fork'.
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?
next prev parent reply other threads:[~2006-03-30 1:14 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 ` PAUL GILLIAM [this message]
2006-03-30 4:30 ` GDB paper for GCC summit: New Commands Joel Brobecker
2006-04-01 13:21 ` Eli Zaretskii
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=1143681561.21920.426.camel@dufur.beaverton.ibm.com \
--to=pgilliam@us.ibm.com \
--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