An automated "backtrace" has been added to ntop - in those environment which support it (it is a gcc library extension). If ntop receives a segmentation fault, there will be a backtrace reported in the system log or stdout:
Apr 20 07:42:06 tigger ntop[1277]: ntop caught signal 11 Apr 20 07:42:06 tigger ntop[1277]: *****ntop error: Signal(11) Apr 20 07:42:06 tigger ntop[1277]: backtrace is: Apr 20 07:42:06 tigger ntop[1277]: 1. /lib/i686/libpthread.so.0 [0x404e5a85] Apr 20 07:42:06 tigger ntop[1277]: 2. /lib/i686/libc.so.6 [0x4054b928] Apr 20 07:42:06 tigger ntop[1277]: 3. /usr/lib/libntop-2.so.0(getHostInfo+0x9ce) [0x402893ce] Apr 20 07:42:06 tigger ntop[1277]: 4. /usr/lib/libntop-2.so.0 [0x40291962] Apr 20 07:42:06 tigger ntop[1277]: 5. /usr/lib/libntop-2.so.0(processPacket+0x16e9) [0x402955d5] Apr 20 07:42:06 tigger ntop[1277]: 6. /usr/lib/libpcap.so.0.6.2 [0x404bbc9e] Apr 20 07:42:06 tigger ntop[1277]: 7. /usr/lib/libpcap.so.0.6.2(pcap_dispatch+0x36) [0x404bcdea] Apr 20 07:42:06 tigger ntop[1277]: 8. /usr/lib/libntop-2.so.0(pcapDispatch+0x151) [0x4028ec79] Apr 20 07:42:06 tigger ntop[1277]: 9. /lib/i686/libpthread.so.0 [0x404e2c6f] Apr 20 07:42:06 tigger ntop[1277]: 10. /lib/i686/libc.so.6(__clone+0x3a) [0x4060a4fa] Apr 20 07:42:06 tigger ntop[1277]: Cleaning up... Looking for meaningful names, you'll see getHostInfo + 0x9ce (You will note that the offset in the function is in hex). If you're reporting a segmentation fault, be sure to include the backtrace in addition to all the other information. The code has been available for a while, the automated activation went into the cvs 20Apr2002, available in the 21Apr2002 snapshot. -----Burton _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listmanager.unipi.it/mailman/listinfo/ntop
