Hijack: Connect to an existing process with irb

elliterate · July 10, 2009, 3:55am

Hi,

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

I’m sure the benefits of this are pretty obvious

Github page: GitHub - ileitch/hijack: Provides an irb session to a running ruby process.

Hope someone finds it useful!

Cheers

elliterate · July 10, 2009, 9:06am

Great. Could you tell me what’s the difference from live-console?

elliterate · July 12, 2009, 5:27am

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

gist.github.com

https://gist.github.com/tmm1/145471

em-irb-console.rb

require 'rubygems'
require 'eventmachine'

module Console
  PROMPT = "\n>> ".freeze

  def post_init
    send_data PROMPT
    send_data "\0"
  end

This file has been truncated. show original

=r

elliterate · July 14, 2009, 10:07pm

I’ve just changed Hijack so that you can hijack any Ruby process - no
need
for your target process to require any code before it can be hijacked.
It
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
to.

This should make it a lot more useful as most people probably wouldn’t
think
about using something like LiveConsole until a problem is known… at
which
point you have to enable LiveConsole in your app, restart it and then
wait
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 P. [email protected]