Wireshark-bugs: [Wireshark-bugs] [Bug 9867] New: Random exit due to "Broken Pipe: 13" on OSX

Date: Mon, 10 Mar 2014 18:03:41 +0000
Bug ID 9867
Summary Random exit due to "Broken Pipe: 13" on OSX
Classification Unclassified
Product Wireshark
Version 1.11.x (Experimental)
Hardware x86-64
OS Mac OS X 10.9
Status UNCONFIRMED
Severity Major
Priority Low
Component Wireshark
Assignee [email protected]
Reporter [email protected]

Build Information:
/Applications/Wireshark.app/Contents/MacOS/Wireshark -v
FIX: packet list heading menu sensitivity 
wireshark 1.11.2 (SVNRev 53411 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 Qt 5.1.1 with GLib 2.36.0, with libpcap, with libz
1.2.3,
without POSIX capabilities, with SMI 0.4.8, without c-ares, without ADNS, with
Lua 5.1, without Python, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT
Kerberos, with GeoIP, without PortAudio, with AirPcap.

Running on Mac OS X 10.9.2, build 13C64 (Darwin 13.1.0), with locale
en_US.UTF-8, with libpcap version 1.3.0 - Apple version 41, with libz 1.2.5,
GnuTLS 2.12.19, Gcrypt 1.5.0, without AirPcap.
       Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz

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

--
Wireshark has been randomly exiting on various dialogs or actions for me.  The
exit is abrupt, but does not bring up the OSX standard application crash/hang
dialog.  However, in the OSX console.app, there are a couple notable logs,
similar to:

3/10/14 10:39:02.981 AM Wireshark[94984]: modalSession has been exited
prematurely - check for a reentrant call to endModalSession:
3/10/14 10:39:11.237 AM com.apple.launchd.peruser.2528[187]:
(org.wireshark.Wireshark.86272[94984]) Exited abnormally: Broken pipe: 13

I haven't been able to find an exact series of steps to reproduce at this time,
but in a couple hours of use, it has crashed nine times, so it's fairly easy to
see by simple use.  I'll update if I find something concrete.  In the meantime
if there is some logs or otherwise I can provide, please let me know.


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