[Soot-list] error when running paddle

[Chengnian Sun]

Hi,

I ran the example paddle in soot, and got the following error.

Is it because of memory constraints, or it is a bug from SUN JVM?

Also, I found it was slow? Any suggestion?

Thanks.


Warning: Method <java.security.Provider$Service: java.lang.Object
newInstance(java.lang.Object)> is reachable, and calls Class.newInstance,
and you didn't specify any dynamic classes; graph may be incomplete! Use
safe-newinstance option for a conservative result.
Major iteration:
Warning: Method <java.security.Provider$Service: java.lang.Object
newInstanceGeneric(java.lang.Object)> is reachable, and calls
Class.newInstance, and you didn't specify any dynamic classes; graph may be
incomplete! Use safe-newinstance option for a conservative result.
Warning: Method <java.util.logging.LogManager$7: java.lang.Object run()> is
reachable, and calls Class.newInstance, and you didn't specify any dynamic
classes; graph may be incomplete! Use safe-newinstance option for a
conservative result.
Major iteration:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb49b1ee8, pid=17247, tid=3075132304
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode, sharing
linux-x86 )
# Problematic frame:
# C  [libjeddbuddy.so+0x26ee8]  bdd_makenode+0x58
#
# An error report file with more information is saved as:
# /home/neo/workspace/sunix/soot/hs_err_pid17247.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#


-- 
Best Regards.

Chengnian SUN.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20100127/88ded051/attachment.html