[sf-perl] 100 levels deep in subroutine calls!

[Loo, Peter # PHX]

Actually I did not break until a certain condition was met.  Then I
started to step through the code surrounding this failing database
connection.  For example:

DB<1> b 325 $etl_tbl_gid == 170

Then I let the program go until I was prompted again. 
 
Peter

-----Original Message-----
From: Randal L. Schwartz [mailto:merlyn at stonehenge.com] 
Sent: Tuesday, June 19, 2007 9:35 AM
To: Loo, Peter # PHX
Cc: San Francisco Perl Mongers User Group
Subject: Re: [sf-perl] 100 levels deep in subroutine calls!

>>>>> "Loo," == Loo, Peter # PHX <Peter.Loo at source.wolterskluwer.com>
writes:

Loo,> Is this strictly a Perl debug error message or is this a generic
Perl Loo,> error message?  Is there a way around this limitation?  I saw
something Loo,> while searching on the Internet about setting the
$DB::deep to a higher Loo,> number.

Why are you recursing on every line?  Can you flatten your call stack?
Perhaps by gathering all the data first, then acting on it, rather than
acting on it as you see each line.

I've *never* hit the nested-100-deep limit except by accident (or
deliberately).

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777
0095 <merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl
training!


This E-mail message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information.  Any unauthorized
review, use, disclosure or distribution is prohibited.  If you are not
the intended recipient, please contact the sender by reply E-mail, and
destroy all copies of the original message.