I've never seen or used that call, but it sounds a lot more like a glibc function than a system call.
/ Niels Möller ()
Previous text:
2003-02-12 22:36: Subject: Re: Weird problem with Image.SVG in Pike 7.4/7.5
Again, gdb/strace output would be good. That way there would be a way to see where it actually dies.
By the way, an unrelated suggestion - how about adding support for the 'backtrace()' system call on platforms where it's available? It can be used to, on crashes (or demand) craate a stack trace such as this:
Stack dump: { /lib/i686/libpthread.so.0 [0x4003710c] /lib/i686/libc.so.6 [0x401684c8] majesty(Read__17CYLinuxFileSystemiPvUl+0x1d) [0x8268bc1] majesty(Unserialize__11CYLibHeaderi+0x2b) [0x8200b8b] majesty(__11CYLibHeaderi+0x2e) [0x82017d6] majesty(AddLibrary__12CYLibManagerRC8CYString+0x14e) [0x820469e] majesty(AddStaticCAMs__Fv+0x6b) [0x830f0e7] majesty(main+0x5bf) [0x81dcbfb] /lib/i686/libc.so.6(__libc_start_main+0xa2) [0x401573e2] majesty(XMapRaised+0x31) [0x81368b1] }
It's very specific to Linux (afaik) but can prove very useful when trying to debug someone elses problem (i.e it's more information than you would have received otherwise).
/ David Hedbor
