Requiring an empty string causes AIOOB with RubyGems active #445

Closed
headius opened this Issue Dec 15, 2012 · 1 comment

Projects

None yet

2 participants

@headius
Member
headius commented Dec 15, 2012

Pretty self-explanatory...

This is 1.9 mode, with RubyGems active by default. Running 1.8 mode with RG active causes the same error.

See test/test_load.rb:test_require_bogus for a masked test.

system ~/projects/jruby $ jruby -e "require ''"
BaseUTF8Encoding.java:205:in `leftAdjustCharHead': java.lang.ArrayIndexOutOfBoundsException: 24
    from RubyString.java:5215:in `end_with_pCommon'
    from RubyString.java:5195:in `end_with_p'
    from RubyString$INVOKER$i$end_with_p.gen:-1:in `call'
    from CachingCallSite.java:326:in `cacheAndCall'
    from CachingCallSite.java:170:in `call'
    from CallOneArgNode.java:57:in `interpret'
    from AndNode.java:93:in `interpret'
    from NewlineNode.java:105:in `interpret'
    from OrNode.java:100:in `interpret'
    from IfNode.java:110:in `interpret'
    from NewlineNode.java:105:in `interpret'
    from BlockNode.java:71:in `interpret'
    from BlockNode.java:71:in `interpret'
    from RescueBodyNode.java:108:in `interpret'
    from RescueNode.java:177:in `handleException'
    from RescueNode.java:123:in `interpret'
    from ASTInterpreter.java:75:in `INTERPRET_METHOD'
    from InterpretedMethod.java:182:in `call'
    from DefaultMethod.java:188:in `call'
    from MethodHandle.java:599:in `invokeWithArguments'
    from InvocationLinker.java:151:in `invocationFallback'
    from -e:1:in `__file__'
    from -e:-1:in `load'
    from Ruby.java:809:in `runScript'
    from Ruby.java:802:in `runScript'
    from Ruby.java:673:in `runNormally'
    from Ruby.java:522:in `runFromMain'
    from Main.java:390:in `doRunFromMain'
    from Main.java:279:in `internalRun'
    from Main.java:221:in `run'
    from Main.java:201:in `main'
@BanzaiMan BanzaiMan was assigned Dec 15, 2012
@BanzaiMan
Member

Fixed with 2749771.

@BanzaiMan BanzaiMan closed this Dec 15, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment