Philipp Thomas wrote:
On Tue, 26 Feb 2008 18:09:08 +0100, Per Jessen wrote:
Well, the segfault happens in a strlen() call at some point, but removing the vsyslog call "fixes" the problem, so clearly there's something dodgy with vsyslog.
Not necessarily. What's the backtrace you get when running your app under catchsegv (i.e. 'catchsegv your_app')?
# catchsegv /home/per/workspace/nnnnnnnn/bwsatellited -d --verbosity=3 *** Segmentation fault Backtrace: /lib64/libc.so.6(strlen+0x20)[0x2b788a6e1d70] /lib64/libc.so.6(_IO_vfprintf+0x3d3f)[0x2b788a6b334f] /lib64/libc.so.6(__vsyslog_chk+0x3fe)[0x2b788a72bfce] /home/per/workspace/bulwark/bwsatd/../bwcommon.c:62(message)[0x402fd2] /home/per/workspace/bulwark/bwsatd/bwsatd_main2.c:387(main)[0x401b32] /lib64/libc.so.6(__libc_start_main+0xf4)[0x2b788a68bae4] ??:0(_start)[0x401919] Looks pretty much like what I got when running with gdb. Does catchsegv give me anything I wouldn't catch with gdb ? /Per Jessen, Zürich --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-programming+help@opensuse.org