Re: EXCEPTION_ACCESS_VIOLATION since 1.1.3

Ruby JRuby
1

Thanks for your reply. (2) Specifying jruby.jit.exclude=parse solved the
problem and (1) I’ll do my best to specify the symptoms.

Thanks again!

----- Original Message ----
From: Charles Oliver N. [email protected]
To: [email protected]
Sent: Sunday, July 27, 2008 9:05:51 PM
Subject: Re: [jruby-user] EXCEPTION_ACCESS_VIOLATION since 1.1.3

Very interesting! It looks like we can narrow this down to a specific
method in rexml that’s blowing up. Two things you should do:

  1. File a bug for this with all information you have.
  2. Specify jruby.jit.exclude=parse and see if you can reproduce it.

It shouldn’t be hard to hunt down. Ultimately it’s going to be a bug in
the JVM…no piece of bytecode should ever be able to crash the
JVM…but if we can reproduce it here we’ll handle talking to the
HotSpot engineers and finding a workaround in the compiler.

Thanks for the report!

P Heemskerk wrote:

Subject: Re: [jruby-user] EXCEPTION_ACCESS_VIOLATION since 1.1.3

(1957 bytes)

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
2

Another workaround sprang to mind: run with --server to use the HotSpot
server VM. Either way, I’ll look forward to the report.

P Heemskerk wrote:

Subject: Re: [jruby-user] EXCEPTION_ACCESS_VIOLATION since 1.1.3
HotSpot engineers and finding a workaround in the compiler.

----- Original Message ----
From: P Heemskerk [email protected]

Current CompileTask:

http://xircles.codehaus.org/manage_email

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email