This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 3/4] 'catch syscall' feature -- XML support part


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]