Thanks :) I tried to get debugger (gem) hooked up to an invocation of that script, but once it hangs the rdb console goes unresponsive. It's pretty ugly! Fortunately, `gdb -p <process_id>` was still able to attach. You can see the output of a 'where' call to gdb at the end of the same Gist:
https://gist.github.com/bradland/5568217 I think I'd like to open the ticket since I have a debugger running and attached. I have it running on a machine that I can leave idle waiting for additional gdb calls, so that might help the maintainer, given the time it takes to reproduce. Is this you? https://github.com/mccannatron I'll ping you in the issue so you can stay up to speed. On Monday, May 13, 2013 10:54:33 AM UTC-4, Chris McCann wrote: > > Wow, top-notch work, Brad. I'll happily submit this as a ticket as you > suggested and give full credit to you for the sleuthing, unless you'd like > to submit it. > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
