SEQ segfaults after one minute

[Musashi]

My seq has been running normally (with the occasional segfault) for a while now, then I updated from CVS. When I start up the program, it sits for one minute, then segfaults. Doing a backtrace gets:

Core was generated by `showeq'.
Program terminated with signal 11, Segmentation fault.
#0 0x08089246 in ?? ()
(gdb) bt
#0 0x08089246 in ?? ()
#1 0x08088d98 in ?? ()
#2 0x401e8cea in ?? ()
#3 0x4023afa2 in ?? ()
#4 0x4021ea00 in ?? ()
#5 0x401a528f in ?? ()
#6 0x40171608 in ?? ()
#7 0x4016f230 in ?? ()
#8 0x401a733b in ?? ()
#9 0x4016ed98 in ?? ()
#10 0x080627d5 in ?? ()
#11 0x42017499 in ?? ()

When I run the program, I get the following output:
Using config file '/usr/local/share/showeq/showeq.xml'
Loaded preferences file: /usr/local/share/showeq/seqdef.xml!
Loaded preferences file: /usr/local/share/showeq/showeq.xml!
Listening for client: 216.30.143.32
Initializing Packet Capture Thread:
Filtering packets on device eth0, IP host 216.30.143.32
Loading filters from '/usr/local/share/showeq/filters.conf'
No Zone Specific filter file '/usr/local/share/showeq/filters_unknown.conf'.
Loading default '/usr/local/share/showeq/filters.conf'.
Categories Reloaded
Error opening map file '/usr/local/share/showeq/unknown.map'!
Opcode Logging Mask: 0 0 0
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 62.148.196.104:6257] seq 0419 len 137 crc32 (775c03c8 != 12a38d53)
INVALID PACKET: Bad CRC32 [80.195.68.143:6257 -> 216.30.143.32:6257] seq 10e7 len 133 crc32 (3e5b6d6c != 9484a0ac)
INVALID PACKET: Bad CRC32 [80.195.68.143:6257 -> 216.30.143.32:6257] seq b53b len 65529 crc32 (5dc740cb != 396ad881)
INVALID PACKET: Bad CRC32 [4.65.27.185:6257 -> 216.30.143.32:6257] seq 230b len 89 crc32 (db102364 != de65c484)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 4.65.27.185:6257] seq 7c56 len 65534 crc32 (77887a5a != c477573e)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 217.233.112.35:6257] seq 318a len 131 crc32 (20bc93a0 != 1c3b2d86)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 66.188.154.107:6257] seq 8de3 len 119 crc32 (17119030 != e0220af7)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 4.65.27.185:6257] seq 73cb len 85 crc32 (a14d08c6 != acf7fccc)
INVALID PACKET: Bad CRC32 [4.65.27.185:6257 -> 216.30.143.32:6257] seq 246d len 65535 crc32 (81f43def != d6a50b2d)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 141.151.200.194:6257] seq 455c len 259 crc32 (000727ec != b9b92d4f)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 65.189.147.53:6257] seq 6cbe len 65528 crc32 (2d0cc70f != 3dca7bdd)
INVALID PACKET: Bad CRC32 [65.189.147.53:6257 -> 216.30.143.32:6257] seq c05b len 65534 crc32 (a161c7a0 != aaa28f6b)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 24.84.35.156:6257] seq 7bff len 153 crc32 (5220d1ea != 40a53bd5)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 24.84.35.156:6257] seq 261f len 131 crc32 (bc66413f != 44afa67d)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 80.131.209.146:6257] seq 0ab6 len 65528 crc32 (12f8007c != 41664c5c)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 24.128.56.83:6257] seq a9b0 len 119 crc32 (b6c0b13a != 5d5bbd23)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 68.66.177.177:6257] seq 2818 len 105 crc32 (72ae5cda != 80c10401)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 66.126.133.28:6257] seq b6d2 len 10 crc32 (8ead0ff6 != 8454e589)
INVALID PACKET: Bad CRC32 [66.126.133.28:6257 -> 216.30.143.32:6257] seq 102c len 65 crc32 (9ccb71e0 != 26e10d53)
INVALID PACKET: Bad CRC32 [66.126.133.28:6257 -> 216.30.143.32:6257] seq fab1 len 65530 crc32 (a7b3259f != e0133c0a)
INVALID PACKET: Bad CRC32 [216.30.143.32:6257 -> 172.172.83.56:6257] seq b86e len 146 crc32 (12515b94 != f93dfef5)
Segmentation fault

This is on a RH7.3 box - I've updated gcc to the latest RPMs. If you need any more info or have an idea, let me know.

[Dedpoet]

What else do you have going on on your network? Non-EQ traffic could be the cause of this. Some of those IP's look suspicious.

[Musashi]

Yeah, it took me a while to figure out it was traffic to WinMx.. :p

However, stopping that didn't fix the problem. After spending most of the the day checking package versions, updating RPMs, tweaking config files, and whatnot... it turns out my libEQ.a was an older version, and updating that fixed the problem.