Re^2: debug startup problem

I am not using readLine in my program. It is brought in by the Perl debugger due to the -d that I recently added to the first line. Is there any way for me to have control over the aspects that you suggest, in this case?

Comment on Re^2: debug startup problem

Replies are listed 'Best First'.
Re^3: debug startup problem by cmac (Monk) on Nov 19, 2008 at 21:07 UTC
From another forum I have learned that perldb requires STDOUT to be a terminal, so that the ">../to_excel/excnnnnn.txt" in my invocation line caused my problem. This would not have to be the case: the writer on the site where I learned about this feature noted that perldb could find the terminal from any of STDIN, STDOUT, or STDERR, whichever was not redirected. SUGGESTION FOR FUTURE WORK ON perldb!! As it is, I will revise the program to open and use the output file named in ARGV[0], and leave my command line unchanged except for replacing '>' with a space.	[reply]
Re^3: debug startup problem by massa (Hermit) on Nov 20, 2008 at 00:24 UTC
I think but can't test right now that if you put `-MTerm::ReadLine::Gnu` before the `-d` the perl debugger will use that... obviously, you may have to install Term::ReadLine::Gnu first! []s, HTH, Massa (κς,πμ,πλ)	[reply] [d/l] [select]