Wireshark-bugs: [Wireshark-bugs] [Bug 12228] New: Qt wireshark crashed when expanding All in Pac

Date: Thu, 03 Mar 2016 08:06:26 +0000
Bug ID 12228
Summary Qt wireshark crashed when expanding All in Packet Details pane for id-handoverPreparation MasterInformationBlock packet
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Qt UI
Assignee [email protected]
Reporter [email protected]

Created attachment 14395 [details]
crash figure

Build Information:
Version 2.1.0

Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (32-bit) with Qt 5.5.0, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.38.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, with
AirPcap 4.1.0 build 1622.
Intel(R) Core(TM) i5-4310M CPU @ 2.70GHz (with SSE4.2), with 8105MB of physical
memory.
--
reproduce step:
1) open lte signaling log
2) select X2 signlaing packet - X2HandoverRequest
3) righ click "Expand All" menu, then Qt wireshark crashed.

   This crash issue only exists when expading below X2 signlaing paket, no
issue for other signaling packet. And we don't observe crash isseu for previous
wireshark release.

@2016@01@21 21:43:28.867754000] UPOS #280112 2016-01-21T21:43:28.867754-00:00
[0x80003060] UeCallp_1_5_1_0 X2HandoverRequest <asn1>
pdu:
00000083af000007000a000201b4000540020000000b00080045f01000d50010001700070045f010800000000e0082de4440137a1c000e0000a5aad19069bcf96573773a078ac1a839b51896a36888a02cd5420dfc6abcb033030c845880600a21fe80ff010004400e4500092301f00aee0301497a04550004401a4640013d087d00207d00207d00207d0001f00aee0301497a045e82770f108174c99800f0cc131804302001038b1a40ca5503e7f3ab91ff9ffff647fe7feff91ff9eeffe47fe7b7eb91ff9ffffe47fe7efff91ff9ffffe47fe7bfff91ff9ffffe47fe7bbff91ff9ffffe47fe7bbff91ff9ffffe47fe7ffff91ff9ffffe47fdff3ffafa2080088870ca74a92e47058c000000003a92070c001014020038600080981001c3000404b0800e18002022040070c00101042003b000080b21001d300040420800e600020218400730001010420038200080a01001c1000404c0800e080020258400704001010c20038400080a61001c400040430800e58002021840072c00101042003a000080861001d000040410804a7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff9ffffe47fe7ffff91ff402400008c93f400000003f400000003f40000000fd00000001fa00000003f40000000018020095a00001047e3a5040181bf0458490f18b2780c5fc0400051002c14000008d08c2dec13bec908c1c0e13bec908c5c02fa81b4277d9210f4220101807d82ab4001c010879b8c040601f9804878654b001806038a5fc630360c8198358377aaa681a8f002c540435530431b82b2e80905c804c1bf650d00505e285011006835fe0000aa0006009c01e080105060004203582dd0a2303402a280880102003402595aaa91edd0d3d3182211f80202008960fddae100d5000562eadcfb62734b67252a1abf13adefa74df34601aedd6e802f099763c526381f7e900d5002772f62ccef8d28bd25d1de2e56cda668bd6a4d8b596f7e8e4e0f88ee06d3b9dd5bd2840000f408099708045f01000f040010000040000004d4002002f0845f01000d500110000000000004d400200060845f01000f0400100000f0000004d400200980845f01000d500110000000000004d400200070845f01000f040010000380000004d400202380845f01000d500110000020000004d400200150845f01000f0400100000d0000004d400200840845f01000d500110000000000004d400200010052400400000001


You are receiving this mail because:
  • You are watching all bug changes.