ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: fxn@hashref.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91666] [Ruby trunk Bug#14702] On Ruby 2.5.1, tracepoint isn't working on the file that is loaded by load_iseq
Date: Mon, 04 Mar 2019 23:58:04 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-76926.20190304235803.91ed9d8da02cbad0@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-14702.20180420100321@ruby-lang.org

Issue #14702 has been updated by fxn (Xavier Noria).


Hi!

Rails 6 applcations have bootsnap and Zeitwerk enabled by default. Right now, that needs Ruby 2.6 because Zeitwerk sets a trace point on the :class event to support what I call "explicit namespaces".

Just wanted to let you know about this situation, in case you'd like to take it into account for the timeline to ship 5.2.4.

----------------------------------------
Bug #14702: On Ruby 2.5.1, tracepoint isn't working on the file that is loaded by load_iseq
https://bugs.ruby-lang.org/issues/14702#change-76926

* Author: makoto_tajitsu@hotmail.co.jp (Makoto Tajitsu)
* Status: Closed
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* Target version: 
* ruby -v: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: DONE
----------------------------------------
On Ruby 2.5.1, when loading file with RubyVM::InstructionSequence.load_from_binary, TracePoint callback event is not working on loaded file.

## Steps to reproduce

Ruby version.
```
$ ruby -v
# => ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16]
```

The example with `yomikomu` gem which is simply used `load_iseq` and `load_from_binary` method to load file quickly is following.
```ruby
$ YOMIKOMU_AUTO_COMPILE=true bundle exec irb

> TracePoint.trace(:line) { |tp| puts tp.lineno if tp.path == '/path/to/somefile.rb' }
# => #<TracePoint:enabled>

> load '/path/to/somefile.rb'
# 3
# 4
# ...

> require 'yomikomu'

> load '/path/to/somefile.rb'
# no tracepoint callback for line event
```

## Result of reproduce process

tracepoint callback isn't called on loaded file by using load_iseq and load_from_binary.

## Expected result and the reason why you expect

tracepoint callback should be called for any loaded file to debug with debugguer(e.g. byebug).

On Ruby 2.4.3, this example is working correctly, so tracepoint callback is called and output lineno to stdout when loaded file after `require 'yomikomu'`.





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

  parent reply	other threads:[~2019-03-04 23:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-14702.20180420100321@ruby-lang.org>
2018-04-20 10:03 ` [ruby-core:86626] [Ruby trunk Bug#14702] On Ruby 2.5.1, tracepoint isn't working on the file that is loaded by load_iseq makoto_tajitsu
2018-04-30 16:53 ` [ruby-core:86778] " makoto_tajitsu
2018-08-22  2:45 ` [ruby-core:88602] " ko1
2018-10-11 14:20 ` [ruby-core:89372] " nagachika00
2018-10-28 18:22 ` [ruby-core:89609] " alanwucanada
2019-03-04 23:58 ` fxn [this message]
2019-03-05  8:21 ` [ruby-core:91672] " fxn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-76926.20190304235803.91ed9d8da02cbad0@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).