Hey,

I was wondering what is the best way to submit crash logs of non-repeatable VM 
crashes?

E.g. I have this crash log containing:

OS Version:      Mac OS X 10.9.4 (13E28)

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

[...]

Thread 24:: Java: AWT-Shutdown
0   libsystem_kernel.dylib              0x00007fff96923716 __psynch_cvwait + 10
1   libsystem_pthread.dylib             0x00007fff8eeeec3b _pthread_cond_wait + 
727
2   libjvm.dylib                        0x00000001047ca2c8 
os::PlatformEvent::park() + 192
3   libjvm.dylib                        0x00000001047c2c2e 
ObjectMonitor::wait(long, bool, Thread*) + 748
4   libjvm.dylib                        0x0000000104875a40 
ObjectSynchronizer::wait(Handle, long, Thread*) + 202
5   libjvm.dylib                        0x000000010469cd44 JVM_MonitorWait + 156
6   ???                                 0x0000000105c175a8 0 + 4391531944
7   ???                                 0x00000001066d0204 0 + 4402774532
8   ???                                 0x00000001054069d2 0 + 4383074770
9   ???                                 0x00000001053ff4e7 0 + 4383044839
10  libjvm.dylib                        0x00000001046452ce 
JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) 
+ 1710
11  libjvm.dylib                        0x0000000104645a5c 
JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, 
JavaCallArguments*, Thread*) + 356
12  libjvm.dylib                        0x0000000104645c08 
JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, 
Thread*) + 74
13  libjvm.dylib                        0x000000010469665b 
thread_entry(JavaThread*, Thread*) + 124
14  libjvm.dylib                        0x00000001048a6a81 
JavaThread::thread_main_inner() + 155
15  libjvm.dylib                        0x00000001048a81c4 JavaThread::run() + 
450
16  libjvm.dylib                        0x00000001047ce38a java_start(Thread*) 
+ 246
17  libsystem_pthread.dylib             0x00007fff8eeec899 _pthread_body + 138
18  libsystem_pthread.dylib             0x00007fff8eeec72a _pthread_start + 137
19  libsystem_pthread.dylib             0x00007fff8eef0fc9 thread_start + 13

Thread 25 Crashed:: Java: Java2D Queue Flusher
0   libsystem_kernel.dylib              0x00007fff96923866 __pthread_kill + 10
1   libsystem_pthread.dylib             0x00007fff8eeed35c pthread_kill + 92
2   libsystem_c.dylib                   0x00007fff8e64bb1a abort + 125
3   libjvm.dylib                        0x00000001047cdb37 os::abort(bool) + 25
4   libjvm.dylib                        0x00000001048e9d56 
VMError::report_and_die() + 2260
5   libjvm.dylib                        0x00000001047cf6aa 
JVM_handle_bsd_signal + 1131
6   libjvm.dylib                        0x00000001047cbb6b signalHandler(int, 
__siginfo*, void*) + 47
7   libsystem_platform.dylib            0x00007fff952f75aa _sigtramp + 26
8   libawt_lwawt.dylib                  0x00000001220044cc 
OGLSD_SetScratchSurface + 51
9   libawt_lwawt.dylib                  0x00000001220245ae 
Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer + 1594
10  ???                                 0x0000000106786d6a 0 + 4403522922
11  ???                                 0x0000000107a84a24 0 + 4423436836

[...]

Thread 25 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000124fce000  rcx: 0x0000000124fccef8  
rdx: 0x0000000000000000
  rdi: 0x000000000000d307  rsi: 0x0000000000000006  rbp: 0x0000000124fccf20  
rsp: 0x0000000124fccef8
   r8: 0x0000000000000040   r9: 0x0000000124fcce00  r10: 0x0000000008000000  
r11: 0x0000000000000206
  r12: 0x0000000104c29270  r13: 0x00000006c05a5570  r14: 0x0000000000000006  
r15: 0x00000001047d2ed4
  rip: 0x00007fff96923866  rfl: 0x0000000000000206  cr2: 0x0000000124ecb068
  
Logical CPU:     0
Error Code:      0x02000148
Trap Number:     133

[...]

The full log is at http://www.beatunes.com/download/ogl.crash

There seems to be something wrong with OGLSD_SetScratchSurface, but I have no 
way to reproduce this.
This happened with the last 1.8.0_20-ea before the actual release of U20.

Is this something you are interested in looking into, or should I just file a 
bug report at Oracle?

Cheers,

-hendrik

Reply via email to