# Wow! Jamis Buck + blog + GDB + C API == mind blowing coolnes

**URL:** <https://www.ruby-forum.com/t/wow-jamis-buck-blog-gdb-c-api-mind-blowing-coolnes/69701>\
**Category:** Ruby\
**Created:** [September 23, 2006, 12:48am UTC](https://www.ruby-forum.com/t/wow-jamis-buck-blog-gdb-c-api-mind-blowing-coolnes/69701 "2006-09-23T00:48:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pat\_eyler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/858c86/32.png) [@pat\_eyler](https://www.ruby-forum.com/u/pat_eyler)\
**Post date:** [September 23, 2006, 12:48am UTC](https://www.ruby-forum.com/t/wow-jamis-buck-blog-gdb-c-api-mind-blowing-coolnes/69701/1 "2006-09-23T00:48:40Z")

</div>

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](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.

---

<div class="post-metadata">

**Author:** ![pat\_eyler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/858c86/32.png) [@pat\_eyler](https://www.ruby-forum.com/u/pat_eyler)\
**Post date:** [September 23, 2006, 2:10am UTC](https://www.ruby-forum.com/t/wow-jamis-buck-blog-gdb-c-api-mind-blowing-coolnes/69701/2 "2006-09-23T02:10:45Z")

</div>

In message  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid), pat eyler  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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](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.

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

---

<div class="post-metadata">

**Author:** ![pat\_eyler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/858c86/32.png) [@pat\_eyler](https://www.ruby-forum.com/u/pat_eyler)\
**Post date:** [September 23, 2006, 10:29pm UTC](https://www.ruby-forum.com/t/wow-jamis-buck-blog-gdb-c-api-mind-blowing-coolnes/69701/3 "2006-09-23T22:29:54Z")

</div>

> > > > > “S” == Stephen K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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

---

<div class="post-metadata">

**Author:** ![pat\_eyler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/858c86/32.png) [@pat\_eyler](https://www.ruby-forum.com/u/pat_eyler)\
**Post date:** [September 23, 2006, 10:52pm UTC](https://www.ruby-forum.com/t/wow-jamis-buck-blog-gdb-c-api-mind-blowing-coolnes/69701/4 "2006-09-23T22:52:01Z")

</div>

On 9/22/06, Stephen K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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.
