Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: Tracking down "uninitialized value" errs

by Abigail-II (Bishop)
on Jul 30, 2003 at 09:00 UTC ( #279121=note: print w/replies, xml ) Need Help??


in reply to Tracking down "uninitialized value" errs

You could use a WARN handler. Something like:
$SIG {__WARN__} = sub { require "Carp.pm"; Carp::cluck @_; }

This will give you a stack trace of from where the warning occurred.

Abigail

Replies are listed 'Best First'.
Re: Re: Tracking down "uninitialized value" errs
by jest (Pilgrim) on Jul 30, 2003 at 09:25 UTC

    Thank you so much! This led me right to the problem, if rather verbosely.

    It turns out that whilst streamlining my code, I made incorrect use of a hash slice that brought in more values--some of which were undef--than I had intended; these had no effect on the display but generated errors.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://279121]
help
Chatterbox?
[Corion]: GrandFather: Yeah, I'm currently in the same situation - I get DOM node IDs from Chrome, except that they vanish at some point in time, or event, or whatever. My current workaround is to re-fetch the node IDs all the time, but that is slow

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (8)
As of 2017-08-24 07:55 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Who is your favorite scientist and why?



























    Results (365 votes). Check out past polls.

    Notices?