From: samuel@oriontransfer.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:90271] [Ruby trunk Feature#13483] TracePoint#enable with block for thread-local trace
Date: Mon, 03 Dec 2018 21:33:54 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-75384.20181203213353.5bcd119e0fcc32cc@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13483.20170419073857@ruby-lang.org
Issue #13483 has been updated by ioquatix (Samuel Williams).
@ko1 Was there an update to this proposal?
----------------------------------------
Feature #13483: TracePoint#enable with block for thread-local trace
https://bugs.ruby-lang.org/issues/13483#change-75384
* Author: ko1 (Koichi Sasada)
* Status: Rejected
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* Target version: 2.5
----------------------------------------
# Summary
`TracePoint#enable` with block should enable thread-local trace.
# Current behavior
`TracePoint#enable` enables TracePoint for all of threads, even if it called with `do...end` blcok.
```ruby
t1 = Thread.new{
loop{
x = 1
}
}
th = nil
trace = TracePoint.new(:line){|tp|
if th != Thread.current
p th = Thread.current
end
}
trace.enable do
loop{
a = 1
b = 2
}
end
```
This program shows both main thread and thread `t1` hooked by line events.
# Problem
However, usually `trace.enable do ... end` imply the programmer want to enable hooks only for this block, not for other threads.
For example, Ruby's test for TracePoint skips hooks on other threads.
https://github.com/ruby/ruby/blob/trunk/test/ruby/test_settracefunc.rb#L620
# Proposal
`TracePoint#enable` with block should enable thread-local trace.
I believe proposed behavior is easy to use.
# Consideration
(1) It breaks backward compatibility. Is it acceptable?
(2) What happen on created threads? Should inherit thread-local hooks or ignore them?
I want to ask users of `TracePoint`.
Thanks,
Koichi
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2018-12-03 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-13483.20170419073857@ruby-lang.org>
2017-04-19 7:38 ` [ruby-core:80791] [Ruby trunk Feature#13483] TracePoint#enable with block for thread-local trace ko1
2017-05-19 7:31 ` [ruby-core:81260] " ko1
2017-05-26 5:32 ` [ruby-core:81390] " ko1
2017-05-27 9:49 ` [ruby-core:81416] " eregontp
2017-05-30 6:41 ` [ruby-core:81464] " SASADA Koichi
2018-12-03 21:33 ` samuel [this message]
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-75384.20181203213353.5bcd119e0fcc32cc@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).