The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
"Inspecting a live Ruby process", easier if you cheat.

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Max Zone

Posts: 9170
Nickname: dzone
Registered: Jun, 2006

dzone.com is a link-sharing community where member participation determines what gets published
"Inspecting a live Ruby process", easier if you cheat. Posted: Sep 26, 2006 6:34 PM
Reply to this message Reply

This post originated from an RSS feed registered with Ruby Buzz by Max Zone.
Original Post: "Inspecting a live Ruby process", easier if you cheat.
Feed Title: dzone.com: ruby
Feed URL: http://feeds.dzone.com/dzone/ruby
Feed Description: dzone.com: fresh ruby and rails links for developers
Latest Ruby Buzz Posts
Latest Ruby Buzz Posts by Max Zone
Latest Posts From dzone.com: ruby

Advertisement
Are you still adding printf/puts calls and restarting your app to figure what went wrong? Sometimes, the problem is hard to reproduce, or you only discover it in production. You've got a process that exhibits the bug, but you didn't run it under ruby-debug, so there's no choice but kill it and reproduce after adding some code to inspect your program, right?

Read: "Inspecting a live Ruby process", easier if you cheat.

Topic: Three ways to add Ruby Macros Previous Topic   Next Topic Topic: Brunning's 1st Law of System Hassle

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use