[#58120] [ruby-trunk - Feature #9070][Open] Introduce `---` as synonym of `end` keyword — "alexeymuranov (Alexey Muranov)" <redmine@...>
5 messages
2013/11/01
[#58149] [ruby-trunk - Feature #9076][Open] New one-argument block syntax: &. — "asterite (Ary Borenszweig)" <ary@...>
23 messages
2013/11/04
[#58259] [ruby-trunk - Feature #9099][Open] Train emoji lambda operator — "charliesome (Charlie Somerville)" <charliesome@...>
9 messages
2013/11/10
[#58312] [ruby-trunk - Feature #9107][Open] Introduce YES and NO as aliases of true and false — "gsamokovarov (Genadi Samokovarov)" <gsamokovarov@...>
5 messages
2013/11/13
[#58350] [ruby-trunk - Feature #9113][Open] Ship Ruby for Linux with jemalloc out-of-the-box — "sam.saffron (Sam Saffron)" <sam.saffron@...>
59 messages
2013/11/15
[#60851] Re: [ruby-trunk - Feature #9113][Open] Ship Ruby for Linux with jemalloc out-of-the-box
— Eric Wong <normalperson@...>
2014/02/19
Btw, I also hope to experiment with a slab allocator since many internal
[#62721] [ruby-trunk - Feature #9113] Ship Ruby for Linux with jemalloc out-of-the-box
— nobu@...
2014/05/24
Issue #9113 has been updated by Nobuyoshi Nakada.
[#62735] [ruby-trunk - Feature #9113] Ship Ruby for Linux with jemalloc out-of-the-box
— normalperson@...
2014/05/25
Issue #9113 has been updated by Eric Wong.
[#58391] [ruby-trunk - Bug #9119][Assigned] TestTime#test_marshal_broken_offset broken under MinGW — "luislavena (Luis Lavena)" <luislavena@...>
10 messages
2013/11/17
[#58396] [ruby-trunk - Bug #9121][Open] [PATCH] Remove rbtree implementation of SortedSet due to performance regression — "xshay (Xavier Shay)" <contact@...>
15 messages
2013/11/18
[#58404] [ruby-trunk - Feature #9123][Open] Make Numeric#nonzero? behavior consistent with Numeric#zero? — "sferik (Erik Michaels-Ober)" <sferik@...>
40 messages
2013/11/18
[#58411] [ruby-trunk - Bug #9124][Open] TestSocket errors in test-all on Arch 64-bit — "jonforums (Jon Forums)" <redmine@...>
14 messages
2013/11/18
[#58515] [ruby-trunk - Bug #9124] TestSocket errors in test-all on Arch 64-bit
— "jonforums (Jon Forums)" <redmine@...>
2013/11/23
[#58841] [ruby-trunk - Bug #9124] TestSocket errors in test-all on Arch 64-bit
— "jonforums (Jon Forums)" <redmine@...>
2013/12/04
[#58842] Re: [ruby-trunk - Bug #9124] TestSocket errors in test-all on Arch 64-bit
— Eric Wong <normalperson@...>
2013/12/04
"jonforums (Jon Forums)" <redmine@ruby-lang.org> wrote:
[#58452] [ruby-trunk - Bug #9133][Open] logger rotates log files more than expected — "no6v (Nobuhiro IMAI)" <nov@...>
8 messages
2013/11/21
[#58473] Object identity for string hash keys — Andrew Vit <andrew@...>
I'm not sure if this is a bug. I'm creating a hash like this:
5 messages
2013/11/21
[#58490] Re: [ruby-cvs:50910] drbrain:r43767 (trunk): * lib/rubygems: Update to RubyGems master 50a8210. Important changes — Tanaka Akira <akr@...>
2013/11/22 <drbrain@ruby-lang.org>:
4 messages
2013/11/22
[#58492] Re: [ruby-cvs:50910] drbrain:r43767 (trunk): * lib/rubygems: Update to RubyGems master 50a8210. Important changes
— Eric Wong <normalperson@...>
2013/11/22
Tanaka Akira <akr@fsij.org> wrote:
[#58496] [ruby-trunk - Feature #9140][Open] Allow each_with_index to get start index — "rosenfeld (Rodrigo Rosenfeld Rosas)" <rr.rosas@...>
8 messages
2013/11/22
[#58545] [ruby-trunk - Feature #9145][Open] Queue#pop(true) return nil if empty instead of raising ThreadError — "jsc (Justin Collins)" <redmine@...>
9 messages
2013/11/24
[#58599] [ruby-trunk - Bug #9159][Open] [patch] use rb_fstring for internal strings — "tmm1 (Aman Gupta)" <ruby@...1.net>
5 messages
2013/11/26
[#58653] [ruby-trunk - Bug #9170][Open] Math.sqrt returns different types when mathn is included; breaks various gems - this bug can be reproduced in Ruby 1.8 as well — "kranzky (Jason Hutchens)" <JasonHutchens@...>
7 messages
2013/11/28
[#58719] [ruby-trunk - Feature #5446] at_fork callback API — "tmm1 (Aman Gupta)" <ruby@...1.net>
6 messages
2013/11/30
[ruby-core:58250] [ruby-trunk - Bug #9009] Wrong binding when tracing c-calls
From:
deivid (David Rodríguez) <deivid.rodriguez@...>
Date:
2013-11-10 15:47:39 UTC
List:
ruby-core #58250
Issue #9009 has been updated by deivid (David Rodr鱈guez).
=begin
Hi, I've translate your example to use the TracePoint API
This is the example and result:
class IO
def some_method
end
end
puts "true receiver is #{$stdout}\n\n"
TracePoint.trace(:c_call, :call) do |tp|
puts "#{tp.event} #{tp.defined_class} #{tp.method_id}"
puts " apparent receiver = #{tp.self} vs #{tp.binding.eval('self')}"
Thread.current.backtrace_locations(2).each { |loc| puts " #{loc}" }
end
$stdout.write ""
$stdout.some_method
results in
true receiver is #<IO:0x8bf4e58>
c_call IO write
apparent receiver = #<IO:0x8bf4e58> vs main
test.rb:15:in `<main>'
call IO some_method
apparent receiver = #<IO:0x8bf4e58> vs #<IO:0x8bf4e58>
test.rb:2:in `some_method'
test.rb:16:in `<main>'
My comments:
* Seems like the new way to get the receiver is the (({#self})) instance method of the (({TracePoint})) class. However, the documentation states "(({Same as #binding: trace.binding.eval('self')}))", so that should probably be corrected or further explained.
* Regarding c-frames not being pushed onto the frame stack, they actually are, but after the Tracepoint/set_trace_func event. I made the same mistake here: #8538. Have a look at source:vm_insnhelper.c#L1514 and observe how (({vm_push_frame})) is called after (({EXEC_EVENT_HOOK})).
* I still think the behaviour should be consistent and when inside a TracePoint event the current frame should either be already in the backtrace or not, but not behave differently for c methods and ruby methods.
=end
----------------------------------------
Bug #9009: Wrong binding when tracing c-calls
https://bugs.ruby-lang.org/issues/9009#change-42841
Author: yekka (Nikolay Bozhenov)
Status: Open
Priority: Normal
Assignee:
Category:
Target version:
ruby -v: ruby 2.1.0dev (2013-10-04 trunk 43141) [x86_64-linux]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN
When I use set_trace_func to trace ruby code, I get a wrong binding in
case of c-calls. In this case binding.eval("self") is not the receiver
of the call. Whereas in case of ruby-calls binding.eval("self") yields
the receiver of the call.
The underlying problem is that c-calls aren't pushed onto the frame stack.
It seems that currently there is no way to find out the receiver of c-call
inside tracing function.
Example of code:
$ cat test.rb
class IO
def some_method
end
end
puts "true receiver is #{$stdout}\n\n"
set_trace_func proc { |event, file, line, id, binding, classname|
if event == "call" or event == "c-call"
puts "#{event} #{id}:"
puts "\tapparent receiver = #{binding.eval("self")}"
puts "\tbacktrace:"
caller.each { |l| puts "\t\t#{l}" }
puts
end
}
$stdout.write "" # c-call
$stdout.some_method # ruby-call
Execution:
$ ruby test.rb
true receiver is #<IO:0x00000000bed2a0>
c-call write:
apparent receiver = main
backtrace:
test.rb:18:in `<main>'
call some_method:
apparent receiver = #<IO:0x00000000bed2a0>
backtrace:
test.rb:2:in `some_method'
test.rb:19:in `<main>'
Expected result:
true receiver is #<IO:0x00000000bed2a0>
c-call write:
apparent receiver = #<IO:0x00000000bed2a0>
backtrace:
somewhere:in `write'
test.rb:18:in `<main>'
call some_method:
apparent receiver = #<IO:0x00000000bed2a0>
backtrace:
test.rb:2:in `some_method'
test.rb:19:in `<main>'
--
http://bugs.ruby-lang.org/