This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

2.0.1 64 bit version slow, crashing on OS X; 32 bit version working

0

The 32 bit version of wireshark runs smoothly on my system, the 64 bit version barely runs at all and frequently crashes.

Wireshark: Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)

Here are the differences between the 32 and 64 bit builds:

----Compiled (32-bit) with Qt 4.8.6, with libpcap, without POSIX capabilities, with libz 1.2.3, with GLib 2.16.3, with SMI 0.4.8, without c-ares, without ADNS, with Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.4.3, with MIT Kerberos, with GeoIP, with QtMultimedia, without AirPcap.

Running on Mac OS X 10.11.2, build 15C50 (Darwin 15.2.0), with locale C, with libpcap version 1.5.3 - Apple version 54, with libz 1.2.5, with GnuTLS 2.12.19, with Gcrypt 1.4.3.

Built using gcc 4.2.1 (Apple Inc. build 5666) (dot 3).

----Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS, with Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with QtMultimedia, without AirPcap.

Running on Mac OS X 10.11.2, build 15C50 (Darwin 15.2.0), with locale C, with libpcap version 1.5.3 - Apple version 54, with libz 1.2.5, with GnuTLS 2.12.19, with Gcrypt 1.5.0. Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.9.00).


Here is a sample of the crashes:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007fd200000021 Exception Note: EXC_CORPSE_NOTIFY

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000128 Exception Note: EXC_CORPSE_NOTIFY

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY

asked 23 Jan '16, 09:17

brachygraphic's gravatar image

brachygraphic
11113
accept rate: 0%


One Answer:

0

Please file a bug report on the Wireshark Bugzilla, and give the full contents of the crash reports, not just the summary; the stack report is extremely important for debugging purposes. Please attach to the bug all the different crash reports ("different" as in "have different stack traces" or "have different exception types".)

answered 23 Jan '16, 12:56

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196
accept rate: 19%