I think I may have hosed a piece of perl, specifically the debugger.

Aim9b has asked for the wisdom of the Perl Monks concerning the following question:

On an XP laptop, using ActiveState, I was "cleaning up" and when I finished, my perl will not run in -d mode. I suspect I've deleted something I didn't realize I needed.
I downloaded the build again from AS & reinstalled it into a diff dir (AS_Perl588), but it was no help.
perl FileScan.pl works fine,
but when I try the -d arg,
I get the following set of messages.

C:\Dev\Perl_Dev>perl -d FileScan.pl<br> 
Loading DB routines from perl5db.pl version 1.3<br>
Editor support available.<br>

Enter h or `h h' for help, or `perldoc perldebug' for more help.<br>

main::(FileScan.pl:15): $Mode = "";       # Mode = "" Off, "U" Unatten
+ded, "D" Debug<br>
Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call
+ didn't work. <br>The COLUMNS and LINES environment variabl
es didn't work. <br>The resize program didn't work. at C:/AS_Perl588/l
+ib/Term/ReadKey.pm line 362.<br>
Compilation failed in require at C:/AS_Perl588/lib/Term/ReadLine/Perl.
+pm line 64.<br>
 at C:/AS_Perl588/lib/Term/ReadLine/Perl.pm line 64
        Term::ReadLine::Perl::new<br>('Term::ReadLine', 'perldb', 'GLO
+B(0x19223e4)', 'GLOB(0x18beb18)') called at C:/AS_Perl588/l
ib/perl5db.pl line 6066<br>
        DB::setterm called at C:/AS_Perl588/lib/perl5db.pl line 2238<b
+r>
        DB::DB called at FileScan.pl line 15<br>
Debugged program terminated.  Use q to quit or R to restart,<br>
  use o inhibit_exit to avoid stopping after program termination,<br>
  h q, h R or h o to get additional info.<br>
  DB<1> q<br>
[download]

1-Can someone see where I went wrong & bail me out.
2-Should messages like this be in <some type of> tags?
Thanks. UPDATE: Included Code tags.

Comment on I think I may have hosed a piece of perl, specifically the debugger. Download Code

Replies are listed 'Best First'.
Re: I think I may have hosed a piece of perl, specifically the debugger. by moritz (Cardinal) on Jun 03, 2008 at 19:30 UTC
It seems that the debugger can't determine the window size of your terminal. Do other programs that use this information work for you (eg text based editors). What exactly did you "clean up"? 2-Should messages like this be in <some type of> tags? In `<code>...</code>` tags.	[reply] [d/l]
Re^2: I think I may have hosed a piece of perl, specifically the debugger. by Aim9b (Monk) on Jun 03, 2008 at 19:46 UTC
Notepad & VisualSE seem to work, but I don't know if they're considered text-based. Procomm's VT100 emulation works OK. I don't know exactly what I cleaned up, it was a TEMP folder & most of the sub folders were empty. Also, there appeared to be a "saved download history" folder full of shortcuts, etc. I'm usually very careful about what I delete, but none of these folders looked to be "production" files. Hindsight being 20/20, I should have just added an external drive. Could it be a windows issue, & not perl or the debugger? I just have never seen these types of messages. I didn't realize perl NEEDED the terminal size, etc. Thanks.	[reply]
Re: I think I may have hosed a piece of perl, specifically the debugger. by starbolin (Hermit) on Jun 03, 2008 at 20:18 UTC
Perhaps reverting to a previous restore point via XP help? s//----->\t/;$~="JAPH";s//\r<$~~/;{s\|~$~-\|-~$~\|\|\|s \|-$~~\|$~~-\|\|\|s,<$~~,<~$~,,s,~$~>,$~~>,, $\|=1,select$,,$,,$,,1e-1;print;redo}	[reply] [d/l]
Re^2: I think I may have hosed a piece of perl, specifically the debugger. by Aim9b (Monk) on Jun 04, 2008 at 11:51 UTC
Thanks, that was a great idea, but unfortunately not available to me. Corporate 'gurus' control the laptop, the XP, AND (to some extent)me. Also, perl is not too readily accepted here, so I'm really a 'closet perl coder'. I'm proof it's easier to ask for forgiveness, than for permission. It's been this way since the z-80 assembler days. Do it, show them how good it works, & avoid telling them just HOW you did it. ;-) Were it not for this site, I'd have given up long ago. I had hoped that just reinstalling would fix it, but it looks like I'll have to dig a bit deeper. Thanks again for the reply. Next time I'll make my OWN checkpoint (ie Backup) before I start 'cleaning up'.	[reply]