~/talk

Dispelling the dark magic: Inside a Ruby debugger

Talkat RubyConf 2017 · 2017-11-15..11-17· [ruby]
slides:none on file

Demonstrates building a usable Ruby debugger from about 60 lines of code: uses Ruby’s TracePoint line event to detect breakpoints, IRB and binding to open a live REPL, and implements cont/step/step-over by tracking stack depth and exiting IRB. Describes production needs: thread-scoped tracepoints require a C extension, line-tracing is slow so Stackdriver flips the tracer on only near targets, and a bytecode analyzer plus whitelist prevents side effects for the Stackdriver Debugger.

AI-written summary · about

  1. 0:00Start
  2. 0:11Dispelling the dark magic: inside a Ruby debugger November 16, 2017
  3. 30:04Native breakpoint API?
  4. 32:08Side effects *Object state changes *External side effects
  5. 34:45Debuggers (the basics) are straightforward!
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.