develooper Front page | perl.perl5.porters | Postings from April 2008

[patch]perl5db.pl, perl5db.t - LINUX/UNIX/CYGWIN/VMS

Thread Next
From:
John E. Malmberg
Date:
April 27, 2008 22:39
Subject:
[patch]perl5db.pl, perl5db.t - LINUX/UNIX/CYGWIN/VMS
Message ID:
48156304.30201@qsl.net
2nd try to get the forked debugger working on UNIX/LINUX/CYGWIN and VMS.

In perl5db.pl:

1. Fix so that scripts work on VMS the way that they do on 
UNIX/LINUX/CYGWIN.

2. Move code to make sure that $term is defined for forked xterms to the 
xterm_get_fork_TTY instead of in sub TTY.

That prevents it from interfering with debugger scripts.


In perl5db.t:

Since the debugger now supports scripts on VMS, run the test instead of 
skipping it.



Note 1.  Scripting and forked debuggers are not compatible with each 
other at this time.

Note 2.  Closing the forked debugger xterm on CYGWIN hangs the perl 
interpreter.


To do list:

In VMS, /dev/tty should translate to TT: and the reverse when converting 
UNIX / VMS names if the logical name TT exists and is a terminal.  This 
conversion is needed in a wrapper to any I/O routine that accesses a 
filename, so is not a trivial thing to do.

A way to specify (or not) the forked debugger on the command line.

The value of $TERM should have no bearing on if a forked debugger should 
be created.  Requiring a specific value of $TERM just encourages 
incorrect settings of $TERM.

There is no reason that other X11 terminals instead of xterm could not 
be used, so there should be a way of specifying which one should be 
used.  If that is done, then VMS.C should be adjusted so that DECterm 
can be specified.

Thanks,
-John
wb8tyw@qsl.net
Personal Opinion Only

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About