I had a similar problem on gentoo; uDig doesn't starts and I get this
output from the console:
1 udig > ./udig
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x97758f53, pid=5149, tid=3076871872
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b05 mixed mode)
# Problematic frame:
# C [libxul.so+0x8caf53]
#
# An error report file with more information is saved as hs_err_pid5149.log
#
# If you would like to submit a bug report, please visit:
#
http://java.sun.com/webapps/bugreport/crash.jsp
#
./udig: line 26: 5149 Aborted $PRGDIR/private-bin -data ~/uDigWorkspace $@
I have xulrunner version 1.9.0.14 in my system if it matters, and I
don't specify a virtual machine so I think that uDig tries to use his
shipped virtual machine.
This happens with uDig versions 1.1.0 and 1.1.1, while version 1.0.6
seems to work fine.
output from the console:
1 udig > ./udig
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x97758f53, pid=5149, tid=3076871872
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b05 mixed mode)
# Problematic frame:
# C [libxul.so+0x8caf53]
#
# An error report file with more information is saved as hs_err_pid5149.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
./udig: line 26: 5149 Aborted $PRGDIR/private-bin -data ~/uDigWorkspace $@
I have xulrunner version 1.9.0.14 in my system if it matters, and I
don't specify a virtual machine so I think that uDig tries to use his
shipped virtual machine.
This happens with uDig versions 1.1.0 and 1.1.1, while version 1.0.6
seems to work fine.