You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ recorder.flush_trace(Dir.pwd)
36
36
you can currently use it directly with
37
37
38
38
```bash
39
-
ruby trace.rb [--out-dir DIR] <path to ruby file>
39
+
ruby gems/pure-ruby-tracer/lib/trace.rb [--out-dir DIR] <path to ruby file>
40
40
# produces several trace json files in DIR,
41
41
# or in `$CODETRACER_RUBY_RECORDER_OUT_DIR` if DIR is not provided.
42
42
# Defaults to the current directory.
@@ -60,7 +60,7 @@ however you probably want to use it in combination with CodeTracer, which would
60
60
61
61
## Future directions
62
62
63
-
The current Ruby support is a prototype. In the future, it may be expanded to function in a way to similar to the more complete implementations, e.g. [Noir](https://github.com/blocksense-network/noir/tree/blocksense/tooling/tracer).
63
+
The current Ruby support is a prototype. In the future, it may be expanded to function in a way similar to the more complete implementations, e.g. [Noir](https://github.com/blocksense-network/noir/tree/blocksense/tooling/tracer).
64
64
65
65
### Current approach: TracePoint API
66
66
@@ -77,7 +77,7 @@ For other languages, we've used a more deeply integrated approach: patching the
77
77
78
78
#### Create a C extension for the VM, based on the `rb_add_event_hook2`
79
79
80
-
This would be a straigh-forward port of the current code, but developed as a native extension (e.g. in C/C++ or Rust). The expected speedup will be significant.
80
+
This would be a straight-forward port of the current code, but developed as a native extension (e.g. in C/C++ or Rust). The expected speedup will be significant.
81
81
82
82
#### Patching the VM
83
83
@@ -88,7 +88,7 @@ The patching can be done either directly in the source code of the VM or through
88
88
#### Filtering
89
89
90
90
It would be useful to have a way to record only certain intervals within the program execution, or certain functions or modules:
91
-
we plan on expanding the [trace format](https://github.com/metacraft-labs/runtime_tracing/) and CodeTracer' support, so that this is possible. It would let one be able to record interesting
91
+
we plan on expanding the [trace format](https://github.com/metacraft-labs/runtime_tracing/) and CodeTracer's support, so that this is possible. It would let one be able to record interesting
92
92
parts of even long-running or more heavy programs.
0 commit comments