<amiracam[m]>
hi all , is there an ETA for fixing the jruby debugger issue i.e. "java.lang.IllegalArgumentException: unknown event type: c_call" which prevents even startup of the debugger on Windows and MAC , have not tested it on Linux , trying to push a project to production but not having a debugger is really slowing us down, I just created a new ticket , I believe its a known issue, thanks
nirvdrum has joined #jruby
nirvdrum has quit [Ping timeout: 258 seconds]
nirvdrum has joined #jruby
<headius[m]>
amiracam: that is moving along slower than we'd like but it is moving
<headius[m]>
I don't exactly know how that gem integrates into IDEA and Eclipse plugins
nirvdrum has quit [Ping timeout: 258 seconds]
ur5us has quit [Ping timeout: 260 seconds]
<amiracam[m]>
thanks, that does get past that specific issue , but now I'm having an issue breaking into code running on a Vertx verticle, no crash but it just wont' break / halt
<headius[m]>
Could you comment on the issue and confirm that it's fixed? I think this new issue should be filed with ruby-debug
<headius[m]>
it certainly could end up being a JRuby problem but we run a large number of tests of this same hook subsystem
<amiracam[m]>
k, let me test with something more real world scenario but non Vertx, I'll add my comment tomorrow after some additional testing
<headius[m]>
yeah good, the simpler the reproduction the better
<headius[m]>
thanks!
<amiracam[m]>
sure thing, gnite
<headius[m]>
amiracam: fwiw it appears to use the LINE event in our hook subsystem, which has pretty extensive tests already...so I expect the issue may be further up the stack
<headius[m]>
kares: what benchmark did you use in your report?
<headius[m]>
I reviewed it and it looks good but I wanted to see the 11 result locally
<headius[m]>
we probably should start checking in these one-off benchmarks