Nothing much in it (see attachment).

I would think that this "patchDecoder.c:241" error shouldn't be there in the first place ...

EDIT: Ooops, where is the log file I attached? Don't attachments work? Anyway, since it's so small, here it is in full text:

Fri Jun 27 22:42:17 2008
panic(cpu 1 caller 0x001A8CD4): Kernel trap at 0x0017e2eb, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0xff000014, CR3: 0x01546000, CR4: 0x00000660
EAX: 0x00000001, EBX: 0xff000000, ECX: 0x1f2b2000, EDX: 0x1d9c571c
CR2: 0xff000014, EBP: 0x83a13de8, ESI: 0x001fa000, EDI: 0x00000000
EFL: 0x00010286, EIP: 0x0017e2eb, CS: 0x00000008, DS: 0x01000010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x83a13be8 : 0x12b0fa (0x4592a4 0x83a13c1c 0x133243 0x0)
0x83a13c38 : 0x1a8cd4 (0x46280c 0x17e2eb 0xe 0x461fbc)
0x83a13d18 : 0x19ede5 (0x83a13d30 0x267b5e 0x83a13de8 0x17e2eb)
0x83a13d28 : 0x17e2eb (0xe 0xdb40048 0x83140010 0x83a10010)
0x83a13de8 : 0x162127 (0x1d9c571c 0x1fa000 0x0 0x3)
0x83a13f58 : 0x1a8f72 (0x12bf04b0 0x22228000 0x0 0x3)
0x83a13fc8 : 0x19ece6 (0x10867f40 0x0 0x1a20b5 0x1f2b2000)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe248

BSD process name corresponding to current thread: vmware

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)

There was nothing related in vmware.log when I looked shortly afterwards, but the alert panel mentioned some arcane path (/var/folders/BF/...) where I'd find a related log. Unfortunately, I forget to copy this log immediately to another place, and later on, it was gone. I remember from earlier occurrences of this issue that this log did contain presumably useful information.

I can try to provoke this issue again (unfortunately, the error panel does not come up every time the error occurs, and I could not find out how to make sure it does come up – I did check "Enable debugging checks" in the preferences), but only in a week or so, since I'm on a tight schedule currently and cannot afford to provoke a panic right now.


It's my working copy, so it contains all kinds of things, but I'm quite sure the error can be easily reproduced because it's clearly connected to the display driver. There's only one OPENSTEP display driver that works with VMware Fusion, which was developed by a third party (http://www.atomicobject.com/pages/VMWare+Display+Driver) in cooperation with VMware several years ago. Initially, it worked just fine with VMware Fusion, but later on (before the final release of 1.0) suddenly tended to produce these errors when used with UXGA (and later on even SXGA) resolutions. This never lead to kernel panics in VMware 1.x versions, though. The driver works fine on other VMware incarnations besides Fusion.

If it helps and you provide me with an upload link via PM, I could offer you to send you a clean OPENSTEP virtual machine that demonstrates the issue (again, in a week or so).