syscallent.sh and useless END{} ?

[Dmitry V. Levin]

On Sat, Apr 19, 2008 at 04:28:54PM -0400, Mike Frysinger wrote:
> On Saturday 19 April 2008, Dmitry V. Levin wrote:
> > On Wed, Mar 26, 2008 at 07:20:11PM -0400, Mike Frysinger wrote:
> > [...]
> > > double hrm.  this was svn acting up on me again.  sometimes it fails to
> > > detect that a file actually has changes in it.  in this case,
> > > syscallent.sh wasnt fully committed.
> > >
> > > now that i look at it again, i wonder what exactly the purpose of the
> > > END{} block in the awk is for.  it seems to completely pointless in my
> > > eyes.  why generate 100 extra syscalls that are known to be undefined ?
> >
> > That script seems to be designed to prepare syscallent.h templates for
> > later edit by hand; looks like somebody need stub entries, I have no idea
> > why.
> 
> so just leave it alone ?  or can i send a patch to either remove it or make it 
> optional ?

Let's leave it, maybe this hack really helps somebody to generate proper
stub entries.  For example, there are a lot of such entries in
linux/syscallent.h file before SYS_socket_subcall.


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20080420/a761afaa/attachment.bin>