On May 10, 2012, at 10:33 AM, Charles Oliver Nutter wrote:
> Here's a dump of one of the classes in question. Note that offset 7 in
> the invoke method is definitely wrong:
> https://gist.github.com/5a5e49f31bc79ac344b3
>
> Christian so far can't reproduce, but it seems like a strange thing to
>
Here's a dump of one of the classes in question. Note that offset 7 in
the invoke method is definitely wrong:
https://gist.github.com/5a5e49f31bc79ac344b3
Christian so far can't reproduce, but it seems like a strange thing to
be a problem only in my build...
- Charlie
On Thu, May 10, 2012 at 11:
On Thu, May 10, 2012 at 1:24 AM, Michael Haupt wrote:
> hard to tell what's wrong without seeing the bytecode. :-)
Indeed!
> Please set InvokerBytecodeGenerator.DUMP_CLASS_FILES to true to have all
> LFI (NFI, EI) class files serialised. This also enables unique numbering.
> The dumped class fil
Charlie,
Am 10.05.2012 um 06:36 schrieb Charles Oliver Nutter:
> Christian suggested -Xverify:all, which provides
> the following...so I guess something is generating bad code here?
>
> Invalid gemspec in
> [/Users/headius/projects/jruby/lib/ruby/gems/shared/specifications/trinidad_jars-1.0.3.gem
I'm getting a lot of these messages trying to test against meth-lazy,
which is preventing me from validating it for larger benchmarks and
JRuby's test suite:
Invalid gemspec in
[/Users/headius/projects/jruby/lib/ruby/gems/shared/specifications/treetop-1.4.10.gemspec]:
=== DEBUG MESSAGE
