. *\n\n;
100 levels deep in subroutine calls!
Is this strictly a Perl debug error message or is this a generic Perl
error message? Is there a way around this limitation? I saw something
while searching on the Internet about setting the $DB::deep to a higher
number.
I hope you can shed some
Hi Peter
100 levels deep in subroutine calls!
Is this strictly a Perl debug error message or is this a generic Perl
error message? Is there a way around this limitation? I saw something
while searching on the Internet about setting the $DB::deep to a higher
number.
You can easily test
On 6/19/07, Ron Savage [EMAIL PROTECTED] wrote:
Hi Peter
100 levels deep in subroutine calls!
Is this strictly a Perl debug error message or is this a generic Perl
error message? Is there a way around this limitation? I saw something
while searching on the Internet about setting the $DB
:)
After he gets the 100 levels deep in subroutine calls in the Perl
debugger, he should use the T command to view the call stack.
Ronald
On Fri, 15 Jun 2001 14:20:28 -0500 (CDT), Scott T. Hildreth
[EMAIL PROTECTED] wrote:
It appears that you are attempting to enter data to a column that has possible
reached it's max size. What type of column type is the duplicate entry referring
too??
Sorry I should have mentioned that I did
, 2001 2:20 PM
To: Sterin, Ilya
Cc: [EMAIL PROTECTED]
Subject: RE: 100 levels deep in subroutine calls!
Sorry I should have mentioned that I did Trace it,
I traced one of the Statement Handles as well as the
Db Handle, it shows the Duplicate Error being returned
but nothing else,
ERROR
It is updating data, the duplicates come from running again.
Will get so far then it dies. When I took out the eval from
the one function, it stopped dieing there. He has numerous code
changes/fixes to make. He was reusing a global $sth for every
handle, preparing everytime in a
