For those of you who don’t follow Jamis B.'s blog (and why
don’t you?) you should run, not walk, over to
http://weblog.jamisbuck.org/2006/9/22/inspecting-a-live-ruby-process
to get instructions on using GDB and the Ruby C API to get a
stack trace out of a running process. I’m guessing that there
may be more magic hiding in this corner, but Jamis has done a
great job of shining a light into it to get us started.
In message
[email protected], pat eyler
[email protected] writes
For those of you who don’t follow Jamis B.'s blog (and why
don’t you?) you should run, not walk, over to
Buckblog: Inspecting a live Ruby process
to get instructions on using GDB and the Ruby C API to get a
stack trace out of a running process. I’m guessing that there
may be more magic hiding in this corner, but Jamis has done a
great job of shining a light into it to get us started.
The most amazing thing for me (that I get from this thread) is that
people are amazed that gdb is so good when that was obvious in 1990. Its
even better if you run it inside emacs as you can view your source in
one window and gdb in the other (which you could also do in 1990).
Stephen
“S” == Stephen K. [email protected] writes:
S> even better if you run it inside emacs as you can view your source in
S> one window and gdb in the other (which you could also do in 1990).
You don’t need emacs, just hit ^X-2 (Control-X 2) and you’ll have 2
windows
- one with the source
- the other with the assembler
Guy Decoux
On 9/22/06, Stephen K. [email protected] wrote:
In message
The most amazing thing for me (that I get from this thread) is that
people are amazed that gdb is so good when that was obvious in 1990. Its
even better if you run it inside emacs as you can view your source in
one window and gdb in the other (which you could also do in 1990).
The part that excites me is the idea of using GDB with the Ruby C
API to help debug Ruby scripts.
Yes, GDB and emacs have been a cool combination for a long time,
I’m just happy to see another way of using them.