Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re: debugging possible memory crash?

by varian (Chaplain)
on Jun 11, 2007 at 06:40 UTC ( [id://620419]=note: print w/replies, xml ) Need Help??


in reply to debugging possible memory crash?

Indead not really a Perl issue. This is documented xterm behavior, it is supposed to exit as soon as the program it has started has completed. So instead of:
xterm -e 'perl xx.pl'
specify an extra xterm option to keep the window open after the Perl program has finished:
xterm -hold -e 'perl xx.pl'

Replies are listed 'Best First'.
Re^2: debugging possible memory crash?
by Anonymous Monk on Jun 11, 2007 at 06:45 UTC
    I'm running a shell within the xterm. Executing the Perl script takes down both the shell & xterm. This is expected behaviour? I would think I should be returning to the shell...
      once perl exits, xterm does what xterm want

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://620419]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others goofing around in the Monastery: (2)
As of 2024-04-24 23:28 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found