General

Profile

dalehamel (Dale Hamel)

  • Login: dalehamel
  • Registered on: 07/22/2019
  • Last sign in: 10/14/2026

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 2 0 2

Activity

10/15/2026

12:26 PM Ruby Feature #21539: Export symbols for external profiling of stripped shared Ruby builds
## Summary
Exporting the three symbols had no measurable cost on ruby-bench's `lobsters`, with or without ZJIT, on x86-64 or arm64. With default visibility, though, GCC compiles `vm.c` differently, which can move interpreter microbenc...
dalehamel (Dale Hamel)

10/14/2026

05:55 PM Ruby Misc #22417: DevMeeting-2026-11-12
* [Feature #21539] Export symbols for external profiling of stripped shared Ruby builds (dalehamel)
* Reduced scope from earlier ask: export `ruby_current_ec`, `rb_vm_exec`, and `ruby_global_symbols` from shared libruby so external pr...
dalehamel (Dale Hamel)
05:50 PM Ruby Feature #21539: Export symbols for external profiling of stripped shared Ruby builds
Updated the description and subject to reduce the scope of this substantially to just exporting a few symbols dalehamel (Dale Hamel)

08/11/2025

05:07 PM Ruby Feature #21539 (Open): Export symbols for external profiling of stripped shared Ruby builds
## Motivation
External profilers such as [OpenTelemetry's eBPF profiler](https://github.com/open-telemetry/opentelemetry-ebpf-profiler) collect Ruby stacks from outside the Ruby process.
Distribution packages commonly ship shared l...
dalehamel (Dale Hamel)

08/24/2019

05:10 AM Ruby Feature #12093: Eval InstructionSequence with binding
> does this suffice your use case?
Interesting, I'll need to investigate this - it certainly has potential.
My use case is for experimental tracing work, and I basically want to be
able to pre-compile original source with added in...
dalehamel (Dale Hamel)

08/16/2019

02:39 PM Ruby Feature #12093: Eval InstructionSequence with binding
Understood, I’ve closed the pull request. dalehamel (Dale Hamel)
12:36 PM Ruby Feature #12093: Eval InstructionSequence with binding
Yes when I test out Koichi's sample, the iseq look like:
```
disasm: #<ISeq:<compiled>@<compiled>:1 (1,0)-(1,6)> (catch: FALSE)
0000 putself ( 1)[Li]
0001 opt_send_without_...
dalehamel (Dale Hamel)

08/03/2019

02:41 AM Ruby Feature #16027: Update Ruby's dtrace / USDT API to match what is exposed via the TracePoint API
> Could you show us how V8 and Python provide USDT features?
V8 has ustack helpers (which I'd love to try and figure out how to do for MRI) https://www.joyent.com/blog/understanding-dtrace-ustack-helpers which make the type of probing...
dalehamel (Dale Hamel)

08/01/2019

02:12 AM Ruby Feature #16027: Update Ruby's dtrace / USDT API to match what is exposed via the TracePoint API
Thanks for the reply and your work on TracePoints, Koichi.
> I need to study USDT...
I can recommend some resources, I might suggest this excerpt of [my own writing on this](https://bpf.sh/usdt-report-doc/index.html#adding-usdt-s...
dalehamel (Dale Hamel)

07/30/2019

12:32 AM Ruby Feature #16027: Update Ruby's dtrace / USDT API to match what is exposed via the TracePoint API
Hi Martin,
> Do you have any parts implemented already
Yes,I have a prototype gem that adds StaticTracing.tracepoint as a way to define
a stub library that can be used for a debugger (dtrace/bpftrace) to attach
to, similar to the...
dalehamel (Dale Hamel)

Also available in: Atom