On Wed, Dec 10, 2003 at 10:20:23AM -0500, Guillaume Thouvenin wrote: > I try strace to trace the ifconfig executable. > > So I run 'strace -o trace ifconfig eth0 inet 192.168.0.1 netmask 255.255.255.0' > > I'm only interesting by network call. The proble is that the only syscall is > socket(PF_UNIX, SOCK_DGRAM, 0) but socket() is not a syscall, is it? The syscall > is sys_socketcall() no? Correct. sys_socketcall() is one of two multiplexers in the kernel, the other one being sys_ipc(), IIRC. > Is there a way which will allow me to see the call to > sys_socketcall() with its arguments? Should I write a wrapper for > sys_socketcall()? I don't know about strace, sorry, but with (shameless plug) syscalltrack (http://syscalltrack.sf.net), you should be able to track and see the calls to sys_socketcall() itself. At least it's supposed to work, and if it doesn't, it's a bug and I'll fix it ;-) Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/ "the nucleus of linux oscillates my world" - gccbot@#offtopic
Attachment:
signature.asc
Description: Digital signature
