From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: kernel-hacker@bennee.com, gdb@sources.redhat.com
Subject: Re: Break on syscall?
Date: Fri, 19 May 2006 22:06:00 -0000 [thread overview]
Message-ID: <200605192116.k4JLGFkw025170@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060519124834.GA750@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 19 May 2006 08:48:35 -0400)
> Date: Fri, 19 May 2006 08:48:35 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Fri, May 19, 2006 at 11:15:30AM +0100, Alex Bennee wrote:
> > Is it possible to get gdb to break on entering/exiting a syscall (rather
> > than breaking on entering libc or some such)?
>
> This is not supported.
But I think it would be nice if we would support something like "catch
syscall", just like we support "catch fork".
Mark
next prev parent reply other threads:[~2006-05-19 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 10:59 Alex Bennee
2006-05-19 13:43 ` Daniel Jacobowitz
2006-05-19 22:06 ` Mark Kettenis [this message]
2006-05-19 23:13 ` Daniel Jacobowitz
2006-05-20 3:00 ` PAUL GILLIAM
2006-05-21 13:25 ` Daniel Jacobowitz
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=200605192116.k4JLGFkw025170@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kernel-hacker@bennee.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