OpenJDK Zero PPC Build on OS X Leopard

[Kurt Miller]

On Wednesday 14 September 2011 04:24:27 am Konstantin Tokarev wrote:
> 
> 13.09.2011, 19:31, "Kurt Miller" <kurt at intricatesoftware.com>:
> 
> >  On Tuesday 13 September 2011 11:18:15 am Konstantin Tokarev wrote:
> >>   13.09.2011, 18:02, "Kurt Miller" :
> >>>   Ideally you could use my fastdebug w/atomic.diff build to generate the core and make it available to me (compressed). This would allow me to to do a more complete diagnostic on the crash.
> >>>
> >>>   The build is here: http://www.intricatesoftware.com/OpenJDK/macppc/openjdk7-macppc-fcs-fd-atomic-2011-09-12.tar.bz2
> >>   Seems like your host is down
> >>
> >>   http://www.downforeveryoneorjustme.com/www.intricatesoftware.com
> >  Thanks. I switched it to my backup ip. It is up again now.
> >>   I can send my core, though.
> >  It would be better to generate the core using my build so when I debug it here everything matches exactly.
> 
> Attached.

Thank you. I downloaded it and checked it out with gdb. Unfortunately gdb can't unwind
beyond the signal handler so I still can't see where the crash is comming from. :-(

Thread 13 (core thread 12):
#0  0x95269cc8 in nanosleep$NOCANCEL$UNIX2003 ()
#1  0x95262fe0 in usleep$NOCANCEL$UNIX2003 ()
#2  0x9527cc04 in abort ()
#3  0x0158be28 in os::abort ()
#4  0x016d8cd0 in VMError::report_and_die ()
#5  0x011c6bc4 in report_fatal ()
#6  0x01590564 in JVM_handle_bsd_signal ()
#7  <signal handler called>
warning: unrecognized length (0x8fe347d0) for sigtramp context
#8  <signal handler called>
warning: unrecognized length (0x8fe347d0) for sigtramp context
Previous frame identical to this frame (gdb could not unwind past this frame)

Perhaps the source of the crash can be determined with an active gdb session.
I'm building a full debug build now which should contain source line numbers. If the
segfault is caught while gdb is attached having the full debug build will be helpful.
I'll upload it when the build finishes.

Regards,
-Kurt