J
Jay W
I have a PERL script that is executed by NetBackup "bpstart". From within
the script two different lines are launched depending on the Policy passed
to bpstart in %2. Only one of the two lines should be launched at any given
time.
The problem is that shortly after launching the script (about 5 minutes), a
second occurrance starts, then a 3rd, then a 4th .... up to 29 occurances in
some cases. Usually this scenario ends with a Dr Watson abort. The odd thing
is that I use about 7 command line parameters that are identical in each
launch, so a full command line is being "re-executed" :
function: Perl_dounwind
280363f1 b903010000 mov ecx,0x103
280363f6 7417 jz Perl_sv_compile_2op+0x6fa0
(2803ef0f)
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0140FD9C 2805D784 01B31308 015D41C4 28024499 015D41C4 !Perl_dounwind
0140FE24 280862DE 015D41C4 00000000 00000000 505C3A43 !Perl_runops_standard
0140FF3C 00401012 0000000C 015D24B0 015D2AF8 004010F9 !RunPerl
0140FFC0 77E9CA90 00000000 00000000 7FFDF000 C0000005 !<nosymbols>
0140FFF0 00000000 00401016 00000000 000000C8 00000100
kernel32!CreateProcessW
I guess, the questions are :
1. Has anyone else run into this?
2. Is there a syntax that may inadvertantly start another instance of the
command that was originally launched? (I'm 1st year PERL)
I'm trying to prove through debug code that it is NetBackup's fault and not
PERL
Env :
W2K AS - SP4
ActiveState PERL 5.8.1
the script two different lines are launched depending on the Policy passed
to bpstart in %2. Only one of the two lines should be launched at any given
time.
The problem is that shortly after launching the script (about 5 minutes), a
second occurrance starts, then a 3rd, then a 4th .... up to 29 occurances in
some cases. Usually this scenario ends with a Dr Watson abort. The odd thing
is that I use about 7 command line parameters that are identical in each
launch, so a full command line is being "re-executed" :
function: Perl_dounwind
280363f1 b903010000 mov ecx,0x103
280363f6 7417 jz Perl_sv_compile_2op+0x6fa0
(2803ef0f)
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0140FD9C 2805D784 01B31308 015D41C4 28024499 015D41C4 !Perl_dounwind
0140FE24 280862DE 015D41C4 00000000 00000000 505C3A43 !Perl_runops_standard
0140FF3C 00401012 0000000C 015D24B0 015D2AF8 004010F9 !RunPerl
0140FFC0 77E9CA90 00000000 00000000 7FFDF000 C0000005 !<nosymbols>
0140FFF0 00000000 00401016 00000000 000000C8 00000100
kernel32!CreateProcessW
I guess, the questions are :
1. Has anyone else run into this?
2. Is there a syntax that may inadvertantly start another instance of the
command that was originally launched? (I'm 1st year PERL)
I'm trying to prove through debug code that it is NetBackup's fault and not
PERL
Env :
W2K AS - SP4
ActiveState PERL 5.8.1