Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chaoticset (2105)

chaoticset
  (email not shown publicly)
http://chaoticset.perlmonk.org/
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)
JAPH. (That's right -- I'm not Really Inexperienced any more.)

I'm not just here, I'm here [perlmonks.org], and here [javajunkies.org] too, I ramble randomly in my philosophical blog [blogspot.com] and my other blog [blogspot.com]. Soon I'll come in a convenient six-pack.

Journal of chaoticset (2105)

Monday February 23, 2004
10:22 AM

if ( $debugging ) { work_right() } else { fail_miserably() }

[ #17569 ]
Still having trouble getting Net::AIM working. At this point I've stripped out niceties, compared to examples, etc., and can find no significant difference.

(I know, 'significant' in my mind is clearly not quite matching up with 'significant' in terms of actual characters in the code.)

I drag out the debugger section of the Camel and start sticking breakpoints, like voodoo pins, into some of the problem areas. Stepping through the debugger...

...everything works.

I figure I've just missed that it works, and rerun it sans -d. Still doesn't work.

Maybe I'm going insane. I need more coffee. Once that is fetched and I call my father, I'll slap my eyeballs against this thing again and see what falls out.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

if ( $debugging ) { work_right() } else { fail_miserably() } 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • You have a heisenbug! [ic.ac.uk]
  • When this happened to me while working on a network-related task, I found that the time taken in stepping through the code was either allowing an unexpectedly ansyncronous call to complete, or allowing a remote resource to complete (unintentionally asyncronous).

  • I've had this problem before. In my case, I didn't appear to be iterating over a hash properly. However, when I stuck in debugging code to dump the hash, it worked fine. When I dropped to the debugger and manually inspected the hash, it still worked. As it turns out, the problem was because I was calling each on the hash and dying if I had problems. However, I was catching the die in an eval and reentered the subroutine with correct arguments (this was in a test, so you can see why). When I reentered,

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.