[Soot-list] Re: Segmentation fault

[Khilan Gudka]

Sorry, I thought I had tried it on IBM's jvm but I forgot that I hadn't. I
have now tried it and it gives the following error:

JVMDUMP006I Processing Dump Event "systhrow", detail
"java/lang/OutOfMemoryError" - Please Wait.
JVMDUMP007I JVM Requesting Snap Dump using
'/homes/khilan/phd/workspaces/soot/soot/Snap.20080215.163848.23137.0001.trc'
JVMDUMP010I Snap Dump written to
/homes/khilan/phd/workspaces/soot/soot/Snap.20080215.163848.23137.0001.trc
JVMDUMP007I JVM Requesting Heap Dump using
'/homes/khilan/phd/workspaces/soot/soot/heapdump.20080215.163848.23137.0002.phd'
JVMDUMP010I Heap Dump written to
/homes/khilan/phd/workspaces/soot/soot/heapdump.20080215.163848.23137.0002.phd
JVMDUMP007I JVM Requesting Java Dump using
'/homes/khilan/phd/workspaces/soot/soot/javacore.20080215.163848.23137.0003.txt'
JVMDUMP010I Java Dump written to
/homes/khilan/phd/workspaces/soot/soot/javacore.20080215.163848.23137.0003.txt
JVMDUMP013I Processed Dump Event "systhrow", detail
"java/lang/OutOfMemoryError".
Soot has run out of the memory allocated to it by the Java VM.
To allocate more memory to Soot, use the -Xmx switch to Java.
For example (for 400MB): java -Xmx400m soot.Main ...
Exception in thread "main" java.lang.OutOfMemoryError
        at java.util.HashMap.newElementArray(Unknown Source)
        at java.util.HashMap.rehash(Unknown Source)
        at java.util.HashMap.rehash(Unknown Source)

I have tried allocating a heap size up to 1024MB and it still gives this
error.

khilan

On 15/02/2008, Khilan Gudka <khilan.gudka at imperial.ac.uk> wrote:
>
> Dear all,
>
> I am using Soot + Paddle with the Buddy backend and have run into a
> problem. I tried loading JGFSyncBench from the Java Grande Forum benchmark
> but it causes the jvm to segfault. These are the options I am using:
>
> java -Djava.library.path=/path/to/jedd/runtime/lib soot.Main -p cg
> implicit-entry:false -p cg.paddle conf:ofcg,context:kcfa,k:2 -f J -w
> section1.JGFSyncBench
>
> I have tried this with both the 32-bit and 64-bit version of Sun's jvm 1.6as well as IBM's jvm (version 6 also).
>
> Interestingly, it doesn't segfault if I disable paddle, hence I thought it
> might be the jni doing it. However, even if I turn bdds off, i.e. pass
> bdd:false to paddle, it still segfaults.
>
> Any assistance would be greatly appreciated.
>
> Thanks,
> Khilan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20080215/d9fa6e4f/attachment.htm