[#90399] [Ruby trunk Feature#14813] [PATCH] gc.c: make gc_enter+gc_exit pairs dtrace probes, too — ko1@...
Issue #14813 has been updated by ko1 (Koichi Sasada).
3 messages
2018/12/10
[#90417] [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD — naruse@...
Issue #15398 has been reported by naruse (Yui NARUSE).
4 messages
2018/12/11
[#90423] Re: [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD
— Eric Wong <normalperson@...>
2018/12/11
[email protected] wrote:
[#90519] Spoofing warnings for mail from bugs.ruby-lang.org — Charles Oliver Nutter <headius@...>
I'm getting a spoofing warning for emails sent from bugs.ruby-lang.org when
4 messages
2018/12/13
[#90522] Re: Spoofing warnings for mail from bugs.ruby-lang.org
— Eric Wong <normalperson@...>
2018/12/13
Charles Oliver Nutter <[email protected]> wrote:
[#90533] [Ruby trunk Feature#15413] unmarkable C stack (3rd stack) — normalperson@...
Issue #15413 has been reported by normalperson (Eric Wong).
3 messages
2018/12/14
[#90581] [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception — mat999@...
Issue #15424 has been reported by splitice (Mathew Heard).
3 messages
2018/12/17
[#90595] [Ruby trunk Bug#15430] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been reported by hsbt (Hiroshi SHIBATA).
3 messages
2018/12/18
[#90614] [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been updated by hsbt (Hiroshi SHIBATA).
4 messages
2018/12/19
[#90630] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI
— Eric Wong <normalperson@...>
2018/12/20
> It still exists. https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20181218T230003Z.fail.html.gz
[#90820] Re: [ruby-cvs:73697] k0kubun:r66593 (trunk): accept_nonblock_spec.rb: skip spurious failure — Eric Wong <normalperson@...>
[email protected] wrote:
3 messages
2018/12/30
[ruby-core:90410] [Ruby trunk Feature#15287] New TracePoint events to support loading features
From:
ko1@...
Date:
2018-12-10 21:11:57 UTC
List:
ruby-core #90410
Issue #15287 has been updated by ko1 (Koichi Sasada). Eregon (Benoit Daloze) wrote: > How about #source_code or #source or #eval_script instead? I named `eval_script` because we can not get source code other than `*eval` methods (not by `require` and `load`). > instruction_sequence already implies "compiled" so I think the prefix is not needed there too We can get ISeq only on `compiled_script` event. `#instruction_sequence` seems too general for me, and for example, I'm afraid that users can misused at `call/return` event (method's ISeq). This is why I named `raised_exception`, not `exception` (on `raise` event). Not `value` but `returned_value` (on `return` event). But `instruction_sequence` and `eval_script` (`evaled_script`?) can be enough long to detect specific methods for `script_compiled`. ---------------------------------------- Feature #15287: New TracePoint events to support loading features https://bugs.ruby-lang.org/issues/15287#change-75559 * Author: ko1 (Koichi Sasada) * Status: Closed * Priority: Normal * Assignee: ko1 (Koichi Sasada) * Target version: 2.6 ---------------------------------------- # Abstract I propose the following new TracePoint events: * `loaded` (invoked after `require`/`load`) * `method_added` (invoked after method definition) # Background Sometimes we need to hook loading iseq. For example, checking loading files and so on. Also we want to know what kind of methods are defined. For both purpose, we can use some hook methods such as `Module#method_added` and so on. However, defining methods we can override this features. So that if we have two tools/libraries using this feature, they can be conflicted. # Proposal Introduce new TracePoint events: * `loaded` (invoked after `require`/`load`) * `method_added` (invoked after method definition) Also the following methods can be added: * Active only `loaded` event: * `TracePoint#loaded_feature` returns feature name. * `TracePoint#loaded_iseq` returns `RubyVM::InstructionSequence` object (MRI only, internal feature) # Optional proposal Add `class_added` alias name for `class` event. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>