Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: kernel-hacker@bennee.com, gdb@sources.redhat.com
Subject: Re: Break on syscall?
Date: Fri, 19 May 2006 23:13:00 -0000	[thread overview]
Message-ID: <20060519220521.GA16297@nevyn.them.org> (raw)
In-Reply-To: <200605192116.k4JLGFkw025170@elgar.sibelius.xs4all.nl>

On Fri, May 19, 2006 at 11:16:15PM +0200, Mark Kettenis wrote:
> > 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".

Yes, probably.  I think I even started work on this once.  It's just a
bit trickier.  Not only do you want to be able to decode arguments, but
there are other problems... for example, I think procfs allows it, but
traditionally ptrace has no way to request a single step and stop if
entering a syscall, so you'd need an arch hook to detect it to handle
that case.

A nice project for some rainy month :-)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-19 22:06 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
2006-05-19 23:13     ` Daniel Jacobowitz [this message]
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=20060519220521.GA16297@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=kernel-hacker@bennee.com \
    --cc=mark.kettenis@xs4all.nl \
    /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