From: Alex Fenton <aff28@...>
Date: 2007-07-12T23:10:01+09:00
Subject: getting gdb backtrace from ruby exception

Hi

I'm working on a C extension and somewhere in itsomething is raising a 
NoMethodError. The exception is reported with the line of ruby code that 
triggered the bad call in the C extension.

As the C code is large and complex (it's a big SWIG project), I'm having 
trouble finding the problem in the C code. I would use gdb or 
Microsoft's debugger to look at the stack if it was a C error - but when 
a Ruby exception is raised, the process exits and there's no stack to 
inspect.

Ruby's debugger isn't helpful because it only knows about ruby written 
in ruby.

Is there any way I can get at the C stack at the point of ruby 'raise' 
from a C extension?

Thanks
alex