Problems? Is your data what you think it is? | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
after reading the OP again...
have a look at PERLDB_OPTS, especially TTY and noTTY, in perldebug#Configurable Options
After the rc file is read, the debugger reads the $ENV{PERLDB_OPTS} environment variable and parses this as the remainder of a "O ..." line as one might enter at the debugger prompt. You may place the initialization options TTY , noTTY , ReadLine , and NonStop there. If your rc file contains: parse_options("NonStop=1 LineInfo=db.out AutoTrace"); then your script will run without human intervention, putting trace information into the file db.out. (If you interrupt it, you'd better reset LineInfo to devtty if you expect to see anything.) TTY The TTY to use for debugging I/O. noTTY If set, the debugger goes into NonStop mode and will not connect to a TTY. If interrupted (or if control goes to the debugger via explicit setting of $DB::signal or $DB::single from the Perl script), it connects to a TTY specified in the TTY option at startup, or to a tty found at runtime using the Term::Rendezvous module of your choice. This module should implement a method named new that returns an object with two methods: IN and OUT . These should return filehandles to use for debugging input and output correspondingly. The new method should inspect an argument containing the value of $ENV{PERLDB_NOTTY} at startup, or "$ENV{HOME}/.perldbtty$$" otherwise. This file is not inspected for proper ownership, so security hazards are theoretically possible.
Cheers Rolf ( addicted to the Perl Programming Language) In reply to Re: Use Perl Debugger, where input is the output from shell script
by LanX
|
|