A co-worker of mine recently ran into a JVM segmentation fault (!) when
running mxmlc on our project. This happens for both Java 1.5 and 1.6. I
have not seen anything relevant in JIRA about OS X segfaults. Any ideas?
His segfault information follows.
--
Maciek Sakrejda
Truviso, Inc.
http://www.truviso.com
Model: MacBook4,1, BootROM MB41.00C1.B00, 2 processors, Intel Core 2
Duo, 2.4 GHz, 4 GB
Graphics: kHW_IntelGMA965Item, GMA X3100, spdisplays_builtin, 144 MB
java...
$ java -version
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_16-b06-284)
Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing)
the diagnostic message...
Process: java [55236]
Path: /usr/bin/java
Identifier: java
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: bash [51581]
Date/Time: 2009-03-16 16:53:18.806 -0700
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 ??? 0x00000001000051c1 0 + 4294988225
1 ??? 0x000000010000676f 0 + 4294993775
2 ??? 0x0000000100006a1c 0 + 4294994460
3 ??? 0x000000010000504d 0 + 4294987853
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000041 rbx: 0x00007fff5fbfedd0 rcx:
0x0000000000000000 rdx: 0x0000000000000014
rdi: 0x0000000100008708 rsi: 0x552f3d726964706d rbp:
0x00007fff5fbfeb10 rsp: 0x00007fff5fbfeb10
r8: 0x00000000901c45f2 r9: 0x0000000000000000 r10:
0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000014 r13: 0x0000000100008708 r14:
0x0000000000000015 r15: 0x0000000000000000
rip: 0x00000001000051c1 rfl: 0x0000000000010293 cr2:
0x0000000100008708
Binary Images:
0x7fff5fc00000 - 0x7fff5fc2e643 dyld 97.1 (???)
<b40847f1ce1ba2ed13837aeccbf19284> /usr/lib/dyld
