Uh, sorry for the long wait...
That was another problem that occurs with invokedynamic, in particular
with ricochet frames.
I fixed it, pushed the changes and uploaded a new binary to
http://ssw.jku.at/General/Staff/LS/coro/.
- Lukas
On 2011-11-07 00:18, Charles Oliver Nutter wrote:
Ok, bug report time! :)
It looks like it's crashing again once Hotspot JITs.
This works:
jruby --1.9 -Xfiber.coroutines=true bench/bench_fiber_ring.rb 10 100 100
But this doesn't:
jruby --1.9 -Xfiber.coroutines=true bench/bench_fiber_ring.rb 10 1000 100
Here's the console output, and I've attached the log.
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/frame_x86.cpp:312
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error
(/Users/henri/Documents/jenkins/data/jobs/openjdk-1.8-bsdport-x86_64/workspace/sources/hotspot/src/cpu/x86/vm/frame_x86.cpp:312),
pid=21511, tid=4341268480
# assert(sp()<= result + _displacement) failed: monitor end should
be above the stack pointer
#
# JRE version: 8.0
# Java VM: OpenJDK 64-Bit Server VM (23.0-b03-fastdebug mixed mode
bsd-amd64 compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/headius/projects/jruby/hs_err_pid21511.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
Current thread is 4341268480
Dumping core ...
Abort trap
- Charlie
On Sun, Nov 6, 2011 at 6:35 PM, Henri Gomez<henri.go...@gmail.com> wrote:
Ok, I get them and coro is included in OpenJDK 8 from openjdk-osx-build
2011/11/6 Henri Gomez<henri.go...@gmail.com>:
Le 6 nov. 2011 à 22:12, Henri Gomez<henri.go...@gmail.com> a écrit :
Hi to all,
I'm looking for Coro patch by Lukas Stadler, any body knows where I can find it
?
More on this, I found patch here
(http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/ca450b9f8b56), but wondering if
it's allready applied to trunk or in some patch area ?
Thanks for your help/advices
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
