Re: openjdk6 broken on current

On Thu, 2013-05-09 at 17:16 -0500, Larry Rosenman wrote:
> On 2013-05-09 06:16, Damjan Jovanovic wrote:
> > On Wed, May 8, 2013 at 8:52 PM, Larry Rosenman <ler_at_lerctr.org> wrote:
> > On 2013-05-08 13:37, Larry Rosenman wrote:
> > 
> > On 2013-05-08 12:46, Larry Rosenman wrote:
> > On 2013-05-08 12:00, Daniel Eischen wrote:
> > On Wed, 8 May 2013, Daniel Eischen wrote:
> > 
> > On Wed, 8 May 2013, Larry Rosenman wrote:
> > 
> > Daniel Eischen <deischen_at_freebsd.org> wrote:
> > On Wed, 8 May 2013, Larry Rosenman wrote:
> > 
> > Can SOMEONE please look at this?
> > 
> > I have a real need to get java back on my -CURRENT server soon.
> > 
> > Did/can you try just backing out r249606?
> > 
> > --
> > DE
> > 
> > How can I generate a patch to do that?
> > 
> > Go here:
> > 
> > 
> > http://svnweb.freebsd.org/base/head/lib/libthr/thread/thr_sig.c?sortby=date&view=log
> > 
> > then click on "Diff to previous 249606", then click on "Patch"
> > at the top.  You can try backing out each/all of the recent
> > changes to thr_sig.c to see what the culprit is.
> > 
> > You'll have to use "-R" to reverse the patch I believe.
> > 
> > Or, if you have a checked out svn repo, you can always use
> > svn to generate the patch:
> > 
> > $ cd /path/to/svn/src
> > $ svn diff -r249606:249605  # no need to use -R on this patch
> > I've done this, and dealt with a chunk reject, and am recompiling the
> > world.
> > 
> > Will let you know if this fixes it......
> > Still fails.
> > 
> > /bin/mkdir -p
> > 
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/classes/javax/management/remote/rmi
> > rm -f
> > 
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/classes/javax/management/remote/rmi/RMIConnectionImpl_Stub.class
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/bin/java  -Xmx896m
> > -Xms128m -cp /usr/ports/java/openjdk6/work/build/bsd-amd64/classes
> > sun.rmi.rmic.Main -classpath
> > "/usr/ports/java/openjdk6/work/build/bsd-amd64/classes"    \
> > -d /usr/ports/java/openjdk6/work/build/bsd-amd64/classes              \
> > -v1.2                           \
> > -keepgenerated                  \
> > javax.management.remote.rmi.RMIConnectionImpl
> > /bin/mkdir -p
> > 
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/gensrc/javax/management/remote/rmi
> > /bin/cp
> > 
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/classes/javax/management/remote/rmi/RMIConnectionImpl_Stub.java
> > \
> > 
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/gensrc/javax/management/remote/rmi
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/bin/java  -Xmx896m
> > -Xms128m -cp /usr/ports/java/openjdk6/work/build/bsd-amd64/classes
> > sun.rmi.rmic.Main -classpath
> > "/usr/ports/java/openjdk6/work/build/bsd-amd64/classes"    \
> > -d /usr/ports/java/openjdk6/work/build/bsd-amd64/classes              \
> > -iiop -v1.2                     \
> > javax.management.remote.rmi.RMIConnectionImpl
> > gmake[5]: ***
> > 
> > [/usr/ports/java/openjdk6/work/build/bsd-amd64/classes/javax/management/remote/rmi/RMIConnectionImpl_Stub.class]
> > Segmentation fault (core dumped)
> > gmake[5]: *** Deleting file
> > 
> > `/usr/ports/java/openjdk6/work/build/bsd-amd64/classes/javax/management/remote/rmi/RMIConnectionImpl_Stub.class'
> > gmake[5]: Leaving directory
> > `/usr/ports/java/openjdk6/work/jdk/make/com/sun/jmx'
> > gmake[4]: *** [all] Error 1
> > gmake[4]: Leaving directory
> > `/usr/ports/java/openjdk6/work/jdk/make/com/sun'
> > gmake[3]: *** [all] Error 1
> > gmake[3]: Leaving directory 
> > `/usr/ports/java/openjdk6/work/jdk/make/com'
> > gmake[2]: *** [all] Error 1
> > gmake[2]: Leaving directory `/usr/ports/java/openjdk6/work/jdk/make'
> > gmake[1]: *** [jdk-build] Error 2
> > gmake[1]: Leaving directory `/usr/ports/java/openjdk6/work'
> > gmake: *** [build_product_image] Error 2
> > *** [do-build] Error code 1
> > 
> > Stop in /usr/ports/java/openjdk6.
> > *** [build] Error code 1
> > 
> > Stop in /usr/ports/java/openjdk6.
> > 
> > ===>>> make failed for java/openjdk6
> > ===>>> Aborting update
> > 
> > ===>>> Killing background jobs
> > Terminated
> > 
> > ===>>> You can restart from the point of failure with this command 
> > line:
> > portmaster <flags> java/openjdk6
> > 
> > ===>>> Exiting
> > #
> > #
> > 
> > 
> > I **CAN** give SSH/SUDO access to whoever.....
> > 
> > (gdb) bt
> > 
> > #0  0x0000000801e2da93 in JVM_handle_bsd_signal ()
> > from
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/lib/amd64/server/libjvm.so
> > #1  0x0000000800a49136 in swapcontext () from /lib/libthr.so.3
> > 
> > #2  0x0000000800a48d39 in sigaction () from /lib/libthr.so.3
> > #3  0x00007ffffffff1d3 in ?? ()
> > #4  0x0000000800a48c20 in sigaction () from /lib/libthr.so.3
> > #5  0x0000000801ba9540 in Deoptimization::unpack_frames ()
> > from
> > /usr/ports/java/openjdk6/work/build/bsd-amd64/lib/amd64/server/libjvm.so
> > #6  0x0000000803869f7e in ?? ()
> > #7  0x00007fffffbfa450 in ?? ()
> > 
> > #8  0x000000080383b828 in ?? ()
> > #9  0x000000080685e6e0 in ?? ()
> > #10 0x000000080684f000 in ?? ()
> > #11 0x00007fffffbfa4a0 in ?? ()
> > #12 0x00007fffffbfa518 in ?? ()
> > 
> > #13 0x000000080308f000 in ?? ()
> > #14 0x0000000806bac750 in ?? ()
> > 
> > #15 0x0000000803869eb9 in ?? ()
> > #16 0x0000000000000000 in ?? ()
> > (gdb)
> > 
> > That backtrace would probably be clearer if you got it from a debug
> > build of OpenJDK. Also you could find the exact commit that broke it
> > by doing a bisection-search in SVN like "git bisect" would do.
> > 
> > Regards
> > Damjan Jovanovic

> interestingly, I set both DEBUG and FASTDEBUG, and it compiles cleanly 
> now.
> 
> 


Thanks for this hint!

The port java/openjdk6 fails compiling for me with the above specified
error (Segmentation fault) for a couple of weeks now. With the DEBUG
flags set in the port's configuration, it compiles well.

It is very intersting that it seems to depend on the hardware/CPU in
conjunction with LLVMCLANG 3.3, whether this port compiles or not. In my
case, I have two FreeBSD 10.0-CURRENT boxes running Core2Duo CPUs
(E8400, Q6600) on which the port compiles. On an Ivy-Bridge i3-3220, the
port also compiles well, even with -march=native -O3 flags set to the
compiler. But it fails on the Sandy-Bridge-E machine (i7-3930K) with
either -O3 or -O2 (but both ways -march=native set).

oliver