Wireshark-bugs: [Wireshark-bugs] [Bug 9867] Random exit due to "Broken Pipe: 13" on OSX
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 10 Mar 2014 20:21:27 +0000

Comment # 1 on bug 9867 from 
(In reply to comment #0)
> 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

SIGPIPE isn't one of the signals that maps to an exception that pops up the
crash dialog (just as SIGINT, as generated by control-C, doesn't, SIGPIPE,
which can be generated by program A piping to program B, program B crashing and
closing the pipe, and the write to the pipe crashing program A with SIGPIPE in
order to make the pipeline stop - old UNIX tradition there - doesn't do that
either).

That crash would probably be due to Wireshark writing to a pipe or socket
that's been closed out from under it.

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