Forum: Ruby Hijack: Connect to an existing process with irb

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Ian Leitch (Guest)
on 2009-07-10 03:55
(Received via mailing list)

My new project 'Hijack' is pretty much useable now. It lets you connect
an already running ruby process and interact with it using irb as if it
a normal irb session.

I'm sure the benefits of this are pretty obvious :)

Github page:

Hope someone finds it useful!

Marcin Raczkowski (Guest)
on 2009-07-10 09:06
(Received via mailing list)
Great. Could you tell me what's the difference from live-console?
40c8f707cab5f50878cee873881d6b75?d=identicon&s=25 Roger P. (rogerdpack)
on 2009-07-12 05:27
> Great. Could you tell me what's the difference from live-console?

They appear to scratch the same itch :)

Here's a way to do it through EM, too

Ian Leitch (Guest)
on 2009-07-14 22:07
(Received via mailing list)
I've just changed Hijack so that you can hijack any Ruby process - no
for your target process to require any code before it can be hijacked.
does this by first injecting a payload using gdb, then it signals the
process to start up a DRb server which the hijack client then connects

This should make it a lot more useful as most people probably wouldn't
about using something like LiveConsole until a problem is known.. at
point you have to enable LiveConsole in your app, restart it and then
for the problem to arise again.

The code is very new and fragile but it'd be great to get some feedback!

2009/7/11 Roger Pack <>
This topic is locked and can not be replied to.