summaryrefslogtreecommitdiff
path: root/trace_point.rb
Commit message (Collapse)AuthorAgeFilesLines
* Fix commentJeremy Evans2022-03-291-1/+1
|
* Update comment for TracePoint#enableJeremy Evans2022-03-291-1/+1
| | | Co-authored-by: Benoit Daloze <eregontp@gmail.com>
* Avoid trace events in implementation of TracePoint#enableJeremy Evans2022-03-291-2/+2
| | | | | | | | | This is more backwards compatible, and should fix issues with power_assert. Unfortunately, it requires using a sentinel value as the default value of target_thread, instead of the more natural expression used in the original approach.
* Make TracePoint#enable with block target current thread by defaultJeremy Evans2022-03-291-4/+5
| | | | | | | | | | | | If TracePoint#enable is passed a block, it previously started the trace on all threads. This changes it to trace only the current thread by default. To limit the scope of the change, the current thread is only used by default if target and target_line are both nil. You can pass target_thread: nil to enable tracing on all threads, to get the previous default behavior. Fixes [Bug #16889]
* `TracePoint.allow_reentry`Koichi Sasada2021-12-101-0/+16
| | | | | | | | | | | | | In general, while TracePoint callback is running, other registerred callbacks are not called to avoid confusion by reentrace. This method allow the reentrace. This method should be used carefully, otherwize the callback can be easily called infinitely. [Feature #15912] Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
* Add doc for `a_call` and `a_return` events of TracePointMasataka Pocke Kuwabara2021-11-091-0/+2
|
* [DOC] Fix `TracePoint.trace` format [ci skip]Ulysse Buonomo2021-10-301-5/+3
| | | | Signed-off-by: Ulysse Buonomo <buonomo.ulysse@gmail.com>
* Tweak description of TracePoint :line eventJeremy Evans2021-06-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "code" here is too ambiguous. TracePoint events only occur if there is a new statement or expression on that line, not if the line is a continuation of a previous statement or expression and there is no new statement or expression on the line. For example: ``` [ foo, # start of expression, line event bar # continuation of expression, no line event ] [ foo, # start of expression, line event (bar) # new expression, line event ] foo( # start of expression, line event bar # continuation of expression, no line event ) foo( # start of expression, line event (bar) # new expression, line event ) ``` Fixes [Bug #15634]
* Document binding behavior for C call/return events for TracePoint/set_trace_funcJeremy Evans2021-04-261-3/+9
| | | | | | | C methods do not have bindings, so binding returns the binding of the nearest C method. Fixes [Bug #9009]
* [Feature #16513] TracePoint#inspect returns "... file:line" (#3391)Nguyễn Quang Minh2020-08-061-1/+1
| | | | | | | | | * Fix debug documents to match Thread#to_s change (Feature #16412 ticket) * TracePoint#inspect returns "... file:line" (Feature #16513) * Guard older version of Ruby in Tracepoint inspection tests * Focus on current thread only when running TracePoint inspection test
* [Feature #16254] Use `Primitive.func` styleNobuyoshi Nakada2020-06-191-20/+20
|
* [Feature #16254] Use `__builtin.func` styleNobuyoshi Nakada2020-06-191-20/+20
|
* Fix output of example [ci skip]Kazuhiro NISHIYAMA2020-01-051-1/+1
|
* Make TracePoint.stat a singleton method again (#2726)Alan Wu2019-12-041-1/+1
| | | [Bug #16399]
* use builtin for TracePoint.Koichi Sasada2019-11-081-0/+348
Define TracePoint in trace_point.rb and use __builtin_ syntax.
View Lorry Controller Status