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

[1.10.0] trying to run on OSX10.5.8 but crashes on load.

0

Hey,

Every time I launch WS it crashes with the following report... The interesting line is the last one. Does this need to be filed as a bug?

Process: Wireshark [770] Path: /Software/Security/Wireshark.app/Contents/MacOS/Wireshark Identifier: org.wireshark.Wireshark Version: ??? (???) Code Type: X86 (Native) Parent Process: launchd [99]

Date/Time: 2013-06-15 07:41:54.920 +0100 OS Version: Mac OS X 10.5.8 (9L31a) Report Version: 6 Anonymous UUID: 5DCB56D2-C51F-44C6-9413-40CBF6383CE7

Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Crashed Thread: 0

Dyld Error Message: unknown required load command 0x80000022

asked 15 Jun '13, 00:00

ASGR's gravatar image

ASGR
20448
accept rate: 0%

1

I've back-tracked through the previous versions and the last known working version is 1.8.6.

(15 Jun '13, 00:51) ASGR

Had the same problem, MacBookPro 3,1 OS X 10.5.8, current (and prior) version of Wireshark, which at the moment are Wireshark 1.10.1 Intel 32.dmg and Wireshark 1.8.9 Intel 32.dmg. Also tried the last dev. release, Wireshark 1.10.0rc2 Intel 32.dmg and the previous PPC release (since 10.5 has Rosetta, it should work, if slower) Wireshark 1.8.9 PPC 32.dmg. Crashes all around. None worked. Got 1.8.6 Intel from main repository, works!

Links: All OS X Versions

Wireshark 1.8.6 Intel 32.dmg

(28 Jul '13, 11:35) Lubo Diakov

since 10.5 has Rosetta, it should work, if slower

...but it won't support capturing packets, as Rosetta does not understand BPF, the underlying mechanism used by libpcap (and thus by tcpdump, Wireshark, etc.) to capture packets.

(29 Jul '13, 14:27) Guy Harris ♦♦

One Answer:

1

The buildbot being used to build the 32-bit x86 images switched from running Leopard to running Snow Leopard. By default, building on OS X 10.x.y means that the resulting code will run (modulo bugs) on OS X 10.x.y and later, but will not necessarily run on earlier versions - even versions that differ in the "y" (so that something built on 10.5.2 won't necessarily run on 10.5.0 or 10.5.1).

The script used to build support libraries for Wireshark was recently changed to have a flag to build them to target a particular OS X major release, even if built on a Software Update of that release or on a later release, and the configure script for Wireshark was recently changed to have a flag that does the same thing.

(For OS X nerds:

The flag in question 1) causes the software in question to be built against the SDK for that version of the OS and 2) cause it to be built with a -mmacosx-version-min flag that specifies that version. The first makes sure the system libraries against which the software is built are the ones for that OS, so the resulting shared libraries and programs don't expect later versions than those that come with the OS, and the second makes sure various features, including linker features, not available on that version of the OS aren't required by the program; the dyld warning above is saying that a feature only available in Snow Leopard and later is required by the program.)

The buildbots have had support libraries built with the appropriate flag, but they haven't yet been reconfigured to pass the appropriate flag to the configure script. This is being tracked, for the 32-bit version, in Wireshark bug 8986.

answered 28 Jul '13, 13:54

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196
accept rate: 19%

That bug is now closed. If you download Wireshark 1.10.2pre1-51015 Intel 32.dmg or a later Wireshark 1.10.2pre1-XXX Intel 32.dmg build from http://www.wireshark.org/download/prerelease/, and install it, it should work.

Note that, as per bug 8993, the icon in /Applications is invisible. You might have to launch it the first time by doing

open /Applications/Wireshark.app

from the command line; after that, although it's a bit difficult to double-click an invisible icon, it seems to work if you try hard enough. Or you might try clicking or double-clicking on the icon title ("Wireshark") rather than on the area where it would be if it were visible.

(29 Jul '13, 14:26) Guy Harris ♦♦