From: "vo.x (Vit Ondruch)" <v.ondruch@...>
Date: 2012-12-19T22:07:42+09:00
Subject: [ruby-core:50985] [ruby-trunk - Bug #7586] Useless sourceline in DTrace parse__begin and parse__end probes


Issue #7586 has been updated by vo.x (Vit Ondruch).


=begin
Just FYI, this is the output I get testing with SystemTap:

 # stap -e 'probe ruby.parse.begin { printf("*** file: %s line: %d\n", parsedfile, parsedline) }' -c 'ruby --disable-gems -e "eval \"puts 1234\", nil, \"foo\", 8"'
 1234
 *** file: <internal:prelude> line: 1
 *** file: <internal:enc/prelude> line: 1
 *** file: <internal:gem_prelude> line: 1
 *** file: -e line: 1
 *** file: foo line: 8

=end

----------------------------------------
Bug #7586: Useless sourceline in DTrace parse__begin and parse__end probes
https://bugs.ruby-lang.org/issues/7586#change-34863

Author: vo.x (Vit Ondruch)
Status: Closed
Priority: Normal
Assignee: tenderlovemaking (Aaron Patterson)
Category: 
Target version: 
ruby -v: ruby 2.0.0dev (2012-12-17 trunk 38422) [x86_64-linux]


I am not 100% sure, but isn't the 'parser->parser_ruby_sourceline' at https://github.com/ruby/ruby/blob/trunk/parse.y#L5322 always '1'? Does it make sense to pass this information to DTrace  parse__begin(const char *, int) and parse__end(const char *, int) probes?


-- 
http://bugs.ruby-lang.org/