in reply to Make sure you're solving the right problem

I had a similar issue once, where a program would mysteriously fail, mostly when I wasn't looking. What I did, for my case, was to bring up the perl debugger, and watch each line run against a copy of the funky system.

Turned out some chucklehead used signals for detecting timeouts without ever resetting the signal properly... so if the process was fast enough, the new signal handler would go away when the process terminated. Which was quite the case on a dev system.

Use a perl debugger, watch the lines run one by one, and I'd get a signal handler go BOING!.

  • Comment on Re: Make sure you're solving the right problem

Replies are listed 'Best First'.
Re^2: Make sure you're solving the right problem
by talexb (Chancellor) on Oct 13, 2006 at 17:59 UTC

    Absolutely. The Perl debugger is a bit cryptic (OK, it's *very* cryptic), but it shines an intense bright light on what the code's doing. I'm a fan.

    Alex / talexb / Toronto

    "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds