From: Andrew Cagney <cagney@gnu.org>
To: Kip Macy <kmacy@fsmware.com>
Cc: gdb@sources.redhat.com
Subject: Re: System calls debugging
Date: Wed, 11 Feb 2004 18:28:00 -0000 [thread overview]
Message-ID: <402A742F.7000908@gnu.org> (raw)
In-Reply-To: <20040211093618.G17066@demos.bsdclusters.com>
> ld you just type
> (gdb) strace <args>
>
> and have it print out what strace does now while it runs,
> or do you have something more in mind?
who knows, something like:
(gdb) {set,show} strace <see help handle>
or
(gdb) catch syscall all
Catch point 5 created
(gdb) commands 5
silent
backtrace
continue
end
(gdb)
(and don't get me started about that "silent" "feature" :-)
Andrew
next prev parent reply other threads:[~2004-02-11 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 3:55 Kotian, Deepak
2004-02-11 14:32 ` Andrew Cagney
2004-02-11 17:37 ` Kip Macy
2004-02-11 18:28 ` Andrew Cagney [this message]
2004-02-12 11:28 ` Muthukumar
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 11:35 Kotian, Deepak
2004-02-09 20:02 Pending breakpoints and scripts Andrew Cagney
2004-02-09 22:32 ` Daniel Jacobowitz
2004-02-10 21:22 ` Andrew Cagney
2004-02-10 22:26 ` Daniel Jacobowitz
2004-02-11 3:48 ` System calls debugging MuthuKumar-Hotpop
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=402A742F.7000908@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kmacy@fsmware.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