This is the mail archive of the 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 1/4] 'catch syscall' feature -- Architecture-independent part

El mar, 04-11-2008 a las 23:12 +0200, Eli Zaretskii escribiÃ:
> Who said that a syscall is necessarily defined by some number?

I assumed every OS used numbers to define syscalls ...

> More generally, let's say I'd like to implement support for this on
> Windows -- how would I need to go about it?

... but from what you are saying it seems that in Windows it's
different. What's the proper datatype to represent a syscall there?

> > +      /* Checking if the user provided a syscall name or a number.  */
> > +      if (isdigit (cur_name[0]))
> Is the assumption that no name will ever begin with a digit
> universally valid?

Syscall names need to be valid function names in at least the most
common programming languages. I'm far from being a specialist, but isn't
it a very common (or universal?) restriction that function names have to
start with a non-digit character?
Thiago Jung Bauermann
IBM Linux Technology Center

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