Wireshark-bugs: [Wireshark-bugs] [Bug 11367] Self compiled Wireshark fails to run on OS X
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 16 Jul 2015 03:06:17 +0000

Comment # 6 on bug 11367 from 
Pro tip: don't ever run Wireshark with an environment variable that would cause
a program to emit extra output to the standard output, unless you've configured
it not to use libpcap/WinPcap; otherwise, it'll fire up dumpcap, and dumpcap
will spew extra messages to the standard output and error, and those will be
piped to Wireshark, which will get Very Confused as a result of seeing, for
example, spew from the run-time linker about libraries it's loaded when it's
expecting to get messages from dumpcap.

Discovered with some debugging code:

    Error from pipe_read_block from child: Undefined error: 0, msg Unknown
message from dumpcap, try to show it as a string: dyld: loaded:
/Users/gharris/src/cmd/build/./run/Wireshark.app/Contents/MacOS/dumpcap

That would explain the hang.

So try running without DYLD_PRINT_LIBRARIES=1 in mdoit.  Yes, it'd be nice if
we could handle this more robustly; at least on UN*X, we might be able to do
that by using descriptors *other* than the standard output and error for
communications between Wireshark and dumpcap.

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