| Summary: | jruby stacks are does not appear when rubyrunnable is not in the stacktrace | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] MAT | Reporter: | Dimitar Giormov <dimitar.giormov> | ||||
| Component: | Core | Assignee: | Project Inbox <mat.core-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | krum.tsvetkov | ||||
| Version: | 1.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dimitar Giormov
Created attachment 195075 [details]
added more scenarios including Main Thread
More scenarios where Ruby code can be called.
Basically there are 3 approaches that are covered now.
1. When the code is run in RubyRunnable
2. When the code is run in pure Java Thread
3. When the code is run in JRuby Main class
Comment on attachment 195075 [details]
added more scenarios including Main Thread
Thanks for reporting the problem and sending us a patch.
I reveied and tested the patch.
I checked it in with revision 1122.
I added the iplog flag and am closing the message now, as the patch resolves the problem. |