| Bug ID |
8329
|
| Summary |
SIP/SDP context changes generate "GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed"
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.9.x (Experimental)
|
| Hardware |
x86
|
| OS |
Mac OS X 10.8
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 9997 [details]
The pcap to reproduce the bug.
Build Information:
Version 1.9.0 (SVN Rev 47651 from /trunk)
Copyright 1998-2013 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.15, with Cairo 1.12.14, with Pango 1.32.5,
with
GLib 2.34.3, with libpcap, with libz 1.2.7, without POSIX capabilities, without
libnl, without SMI, without c-ares, without ADNS, with Lua 5.1, without Python,
with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, without GeoIP,
without PortAudio, with AirPcap.
Running on Mac OS X 10.8.2, build 12C60 (Darwin 12.2.0), with locale
en_US.UTF-8, with libpcap version 1.3.0, with libz 1.2.7, GnuTLS 2.12.19,
Gcrypt
1.5.0, without AirPcap.
Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.11.00).
--
When opening the attached pcap file, every now and then I get this on the
console:
(wireshark:23098): GLib-CRITICAL **: g_hash_table_insert_internal: assertion
`hash_table != NULL' failed
Bug 2368 introduced a "context" for SIP SDP offer/answer negotiation, which I
believe was the beginning of the trail for this bug. Bug 2992 is also related.
After those were submitted in trunk, wireshark would routinely crash on the
attached pcap file, with a segfault due to either access violation or integer
divide by zero.
Luckily someone else saw this and fixed it with rev 47638 and 47639 (but no bug
was submitted afaict). So now it no longer crashes, but it does produce the
above error sometimes. I think this new error is related to the previous
crashing case because when it previously crashed I used GDB to follow it, and
the backtrace was always also in the g_hash_table_insert routine when it
crashed, and always on the same packet as this error is spit out for.
This always happens on dissecting the last packet in the attached pcap - both
when it previously crashed, and for the new GLib-CRITICAL message being
displayed.
Lastly, I'd like to note that the fix for the previous crashing is still
brittle - there are other response codes that can carry an SDP answer; and
there are times when a SIP response can carry an SDP *offer*; and of course
wireshark is used to dissect invalid SIP SDP offer/answer behavior anyway; and
in no case should it crash wireshark.
You are receiving this mail because:
- You are watching all bug changes.