On Jul 12, 2011, at 8:26 PM, Flavio Truzzi wrote: > Program received signal SIGABRT, Aborted. > 0x00007ffff5c57795 in raise () from /lib/libc.so.6 > (gdb) backtrace > #0 0x00007ffff5c57795 in raise () from /lib/libc.so.6 > #1 0x00007ffff5c58c0b in abort () from /lib/libc.so.6 > #2 0x00007ffff5c9072e in ?? () from /lib/libc.so.6 > #3 0x00007ffff5c9666a in ?? () from /lib/libc.so.6 > #4 0x00007ffff5c9a54c in free () from /lib/libc.so.6 > #5 0x00007ffff7bbd37a in ?? () from /usr/lib/libpcap.so.1 > #6 0x00007ffff7bbf7be in icode_to_fcode () from /usr/lib/libpcap.so.1 > #7 0x00007ffff7bb4576 in pcap_compile () from /usr/lib/libpcap.so.1 > #8 0x000000000040139f in Filter::Filter(std::basic_string<char, > std::char_traits<char>, std::allocator<char> >, pcap*) () > #9 0x0000000000401194 in main ()
That's probably due to *something* corrupting the allocation arena, whether it's libpcap or the application. Is there a way to get the OS's memory allocator to run in a mode where it does some stricter checking, or could the program be run under something such as valgrind to see who's going outside the bounds of something it's allocated? - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
