Latest Wireshark crashes on startup
Adam Dershowitz Ph.D., P.E.
dersh at alum.mit.edu
Wed Mar 11 05:32:56 PDT 2015
On Mar 11, 2015, at 5:02 AM, Mark Lucas <mllists at arc.co.uk> wrote:
> The latest MacPorts upgrade to Wireshark 1.12.4, which updated without a problem, now reliably crashes when trying to start it up. Previous version worked fine.
> I have the Wireshark app 1.99.2 also installed which still works ok.
>
> When starting from the terminal MacPorts Wireshark crashes with;-
>
> Segmentation fault: 11
>
> The start of the OS X crash log reports;-
>
>
> Process: wireshark [6175]
> Path: /opt/local/bin/wireshark
> Identifier: wireshark
> Version: 0
> Code Type: X86-64 (Native)
> Parent Process: bash [6165]
> Responsible: Terminal [6161]
> User ID: 501
>
> Date/Time: 2015-03-11 08:46:12.820 +0000
> OS Version: Mac OS X 10.9.5 (13F1066)
> Report Version: 11
> Anonymous UUID: 0EA542C5-0225-B550-A26F-14062DC83078
>
>
> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>
> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0xffffffffd884e000
>
> VM Regions Near 0xffffffffd884e000:
> --> shared memory 00007ffffff83000-00007ffffff84000 [ 4K] r-x/r-x SM=SHM
>
>
> Application Specific Information:
> wireshark 1.12.4 (Git Rev Unknown from unknown)
>
> Compiled (64-bit) with GTK+ 2.24.25, with Cairo 1.14.0, with Pango 1.36.8, with
> GLib 2.42.2, with libpcap, with libz 1.2.8, without POSIX capabilities, with SMI
> 0.4.8, without c-ares, with ADNS, with Lua 5.2, without Python, with GnuTLS
> 3.3.13, with Gcrypt 1.6.3, with MIT Kerberos, with GeoIP, with PortAudio
> V19-devel (built Feb 8 2014 04:53:37), with AirPcap.
>
> Running on Mac OS X 10.9.5, build 13F1066 (Darwin 13.4.0), with locale
> en_GB.UTF-8, with libpcap version 1.6.2, with libz 1.2.8, GnuTLS 3.3.13, Gcrypt
> 1.6.3, without AirPcap.
> Intel(R) Xeon(R) CPU E5520 @ 2.27GHz
>
> Built using clang 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57).
>
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 libgobject-2.0.0.dylib 0x0000000110e1f855 g_type_check_instance_is_fundamentally_a + 11
> 1 libgobject-2.0.0.dylib 0x0000000110e0a959 g_object_ref + 19
> 2 libglib-2.0.0.dylib 0x0000000110e70961 g_list_foreach + 34
> 3 libgtk-x11-2.0.0.dylib 0x00000001106ae560 gtk_window_set_icon_list + 95
> 4 wireshark 0x000000010c41f09f window_icon_realize_cb + 190
> 5 libgobject-2.0.0.dylib 0x0000000110e05b3a g_closure_invoke + 272
> 6 libgobject-2.0.0.dylib 0x0000000110e18eee signal_emit_unlocked_R + 2135
> 7 libgobject-2.0.0.dylib 0x0000000110e19af8 g_signal_emit_valist + 1948
> 8 libgobject-2.0.0.dylib 0x0000000110e1a23a g_signal_emit + 134
> 9 libgtk-x11-2.0.0.dylib 0x00000001106a05ee gtk_widget_realize + 201
> 10 wireshark 0x000000010c3de33f splash_new + 37
> 11 wireshark 0x000000010c4259e0 main + 1046
> 12 libdyld.dylib 0x00007fff8aa905fd start + 1
>
> Thread 0 crashed with X86 Thread State (64-bit):
> rax: 0x0000000000000000 rbx: 0xffffffffd884e000 rcx: 0x0000000000000004 rdx: 0x0000000000000000
> rdi: 0xffffffffd884e000 rsi: 0x0000000000000050 rbp: 0x00007fff538412c0 rsp: 0x00007fff538412c0
> r8: 0x0000000000000000 r9: 0x00007fff53840a00 r10: 0x00000001108104c0 r11: 0x00000001106ae501
> r12: 0x00007f9ada3004f0 r13: 0x00007f9ad843b660 r14: 0x0000000000000000 r15: 0x0000000110e0a946
> rip: 0x0000000110e1f855 rfl: 0x0000000000010286 cr2: 0xffffffffd884e000
>
> Logical CPU: 6
> Error Code: 0x00000004
> Trap Number: 14
>
>
> Is anyone else seeing this?
>
>
>
> ___
Yes, I also did the update, but hadn’t tested it until I saw your email. Mine also won’t run at all and gives a segmentation fault 11.
More information about the macports-users
mailing list