need to debug segfault in zmc 1.23.3
Posted: Sat Feb 21, 2009 8:48 pm
Hi,
I'm running a zm 1.23.3 compiled from source on an Ubuntu 8.04 server.
The problem is I get a lot of seg faults of the following kind:
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Got signal (Segmentation fault), crashing]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Signal address is 0xdf9027dc, from 0x805f1e1 ]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x805f1e1]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x805f1e1]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x80602d1]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x8061b6d]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x8065eba]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x804afbd]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7a78450]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc(__gxx_personality_v0+0x20d) [0x804a821]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: INF [Backtrace complete]
Feb 21 18:01:29 xxxxxxx zmdc[24511]: ERR ['zmc -m 3' exited abnormally, exit status 11]
I'd like to debug this somehow, but are a bit stuck.
Although I enabled core dumps (with ulimit -c 1000000 in /etc/profile) I don't
get any from zmc's crashes. This is because they're trapped somehow and dealt with
inside zmc, right?
If I attach gdb to a zmc process PID while it's still alive I get
Feb 21 21:26:59 xxxxxxx zmdc[25679]: INF ['zmc -m 2' crashed, signal 8]
Feb 21 21:26:59 xxxxxxx zmwatch[25729]: INF ['zmc -m 2' stopping at 09/02/21 21:25:14]
Feb 21 21:26:59 xxxxxxx zmdc[25679]: INF [Starting pending process, zmc -m 2]
So again zmc is escaping me...
Could somebody more familiar with ZM please provide a hint how I could investigate
the above seg fault? Any hints welcome.
Please note I'm reasonably fit with C, the gcc toolchain and the posix environment
but I don't know the inner workings of ZM...
Bye,
Chris.
I'm running a zm 1.23.3 compiled from source on an Ubuntu 8.04 server.
The problem is I get a lot of seg faults of the following kind:
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Got signal (Segmentation fault), crashing]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Signal address is 0xdf9027dc, from 0x805f1e1 ]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x805f1e1]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x805f1e1]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x80602d1]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x8061b6d]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x8065eba]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc [0x804afbd]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7a78450]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: ERR [Backtrace: /opt/zm/bin/zmc(__gxx_personality_v0+0x20d) [0x804a821]]
Feb 21 18:01:29 xxxxxxx zmc_m3[24744]: INF [Backtrace complete]
Feb 21 18:01:29 xxxxxxx zmdc[24511]: ERR ['zmc -m 3' exited abnormally, exit status 11]
I'd like to debug this somehow, but are a bit stuck.
Although I enabled core dumps (with ulimit -c 1000000 in /etc/profile) I don't
get any from zmc's crashes. This is because they're trapped somehow and dealt with
inside zmc, right?
If I attach gdb to a zmc process PID while it's still alive I get
Feb 21 21:26:59 xxxxxxx zmdc[25679]: INF ['zmc -m 2' crashed, signal 8]
Feb 21 21:26:59 xxxxxxx zmwatch[25729]: INF ['zmc -m 2' stopping at 09/02/21 21:25:14]
Feb 21 21:26:59 xxxxxxx zmdc[25679]: INF [Starting pending process, zmc -m 2]
So again zmc is escaping me...
Could somebody more familiar with ZM please provide a hint how I could investigate
the above seg fault? Any hints welcome.
Please note I'm reasonably fit with C, the gcc toolchain and the posix environment
but I don't know the inner workings of ZM...
Bye,
Chris.