#33 trunk r135 segfault after a few minutes of runtime

[Jock McKechnie]

Good afternoon;

I've been having some odd luck with trunk (r135) with it segfaulting when it sees certain SIP calls, although I haven't quite worked out what's triggering it yet. I was wondering if you might take a look - from the gdb it appears that 'idx' isn't being set, but I'll leave the diagnosis of that up to the experts.

I'm calling it with:
sudo ./pcapsipdump-0.2trunk-CentOS6.9-debug -f -i eth1 -d /tmp/pcapsipdump/%Y%m%d-%H%M%S-%f-%t-%i.pcap -T28800 -n2125551234

The gdb backtrace and dump, with various internal IPs and numbers replaced with placeholders is attached.

Thank you very much for your help, I'm grateful to have this tool at my disposal.

• Jock

[Aex Aey]

This should be fixed in [r137], thanks for reporting!

[Aex Aey]

What happened here is: idx is not set because current packet was filtered out (didn't match number-filter, option -n), but IPv4 fragmentation code still tried to save this (first) fragment. Since fragmentation code used idx to access calltable, of course, that failed.

Fix moves part of IPv4 fragmentation code that handles first fragment inside "if(idx>=0)" conditional, where it should've been to begin with.

Thanks again for detailed report!

[Jock McKechnie]

I cannot describe to you how impressed I am with the turn around time. Thank you kindly.