But I'm not sure this is the right way to fix this. Can someone comment ?
Thanks,
Pascal.
I've copied the above over to Bug #5855 since your suggested fix also
seems to address recent Buildbot fuzz-test crashes.
Thanks for the report and analysis.
https://bugs.wireshark.org/bugzilla/show_
Hi,
with revision 36849, when I call tshark to decode in verbose mode a pcap
file containing a single packet I get the following backtrace:
tshark -r temp.pcap -V
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb571c8e0 (LWP 11951)]
packet_range_init (range=0xbfd9f550
