![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
JRuby 1.7.2 |
|
Assignee:
|
Unassigned |
|
Components:
|
Core Classes/Modules |
|
Created:
|
04/Jan/13 9:58 PM
|
|
Description:
|
It appears that in JRuby 1.7.2 (and possibly other versions, I've not tested) Thread#backtrace sometimes returns a backtrace for a different Ruby Thread than the one it was called on. The attached test case demonstrates the issue by creating a secondary thread with a distinct backtrace and then dumping backtraces of all Ruby threads:
Output on MRI (1.9.3):
#<Thread:0x007fc60186b5b8 run>
backtrace.rb:7:in `block in <main>'
backtrace.rb:5:in `each'
backtrace.rb:5:in `<main>'
#<Thread:0x007fc602088390 sleep>
backtrace.rb:2:in `block (2 levels) in <main>'
backtrace.rb:2:in `loop'
backtrace.rb:2:in `block in <main>'
Output on JRuby (1.7.2):
#<Thread:0x590948cf run>
backtrace.rb:7:in `backtrace'
backtrace.rb:7:in `(root)'
backtrace.rb:5:in `each'
backtrace.rb:5:in `(root)'
#<Thread:0x708b3bb3 sleep>
backtrace.rb:7:in `backtrace'
backtrace.rb:7:in `(root)'
backtrace.rb:5:in `each'
backtrace.rb:5:in `(root)'
Note that under JRuby we have the same number of Thread instances, and they both have unique IDs, but they both show the same backtrace (that of the main thread).
|
|
Environment:
|
jruby 1.7.2 (1.9.3p327) 2013-01-04 302c706 on Java HotSpot(TM) 64-Bit Server VM 1.6.0_37-b06-434-11M3909 [darwin-x86_64]
Mac OS X 10.8.2
|
|
Project:
|
JRuby
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Ben Weintraub
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
