in reply to Re^6: Broken Net::Telnet::Netscreen module?
in thread Broken Net::Telnet::Netscreen module?
The trace you showed before seems to show that the method error() from Telnet.pm was called and the program died in line 535 of Telnet.pm (there is a die statement there). If I'm right you have to find out why error() is called.
You can do this for example with the debugger. Set a breakpoint at the foreach line in unsetValue() and single step from there. Where exactly does the program stop? If you never reach the breakpoint, move the breakpoint to a previous line on the next run. If the error shows up only on the second run through unsetValue() 'c'ontinue at the first breakpoint and single step at the next stop
You can also do this testing if you put print statements (like print "1\n"; <statements>; print "2\n";) between crucial statements and watch what number you see last. But the debugger is ultimately faster
UPDATE: Just to make sure, /\^-/ searches for a literal '^-' somewhere in the string, not for '-' at the start of the string. That is what you want, right? And hopefully you didn't post the real password of your netscreen firewall, especially if it is accessible from the internet
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^8: Broken Net::Telnet::Netscreen module?
by spivey49 (Monk) on Aug 14, 2008 at 17:22 UTC |