Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] 'catch syscall' feature -- XML support part
Date: Wed, 05 Nov 2008 14:57:00 -0000	[thread overview]
Message-ID: <20081105145645.GB26401@caradoc.them.org> (raw)
In-Reply-To: <uprlau7jj.fsf@gnu.org>

On Wed, Nov 05, 2008 at 06:21:36AM +0200, Eli Zaretskii wrote:
> What happens if I have a list of syscalls that includes some which are
> unsupported by my kernel?  What would happen if I ask GDB to trace
> those unsupported calls?

It will work fine.  We trace all system calls (on the only supported
implementation, and on the other implementations I'm familiar with).
If your application never makes the unsupported system calls, they'll
never come up; if it does, they'll be caught (and on exit, return an
error, most likely but not always ENOSYS).

> In the opposite case (a kernel that supports more syscalls than in the
> list), I understand I get an error message if I request the syscall by
> name, abut I should be able to request it by the number, right?  (This
> should be described in the manual, and perhaps also said in the error
> message.)

That's right.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2008-11-05 14:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04  4:32 Sérgio Durigan Júnior
2008-11-04 13:36 ` Mark Kettenis
2008-11-04 13:47   ` Daniel Jacobowitz
2008-11-04 15:05     ` Sérgio Durigan Júnior
2008-11-04 15:13       ` Daniel Jacobowitz
2008-11-04 15:18         ` Sérgio Durigan Júnior
2008-11-04 15:06   ` Sérgio Durigan Júnior
2008-11-08 19:06     ` Mark Kettenis
2008-11-04 18:41 ` Tom Tromey
2008-11-07  3:46   ` Sérgio Durigan Júnior
2008-11-07 18:24     ` Tom Tromey
2008-11-04 21:20 ` Eli Zaretskii
2008-11-04 22:23   ` Daniel Jacobowitz
2008-11-04 22:27     ` Eli Zaretskii
2008-11-04 22:36       ` Daniel Jacobowitz
2008-11-05  1:02         ` Sérgio Durigan Júnior
2008-11-05  4:22         ` Eli Zaretskii
2008-11-05 14:57           ` Daniel Jacobowitz [this message]

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=20081105145645.GB26401@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@linux.vnet.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