Debugging advice needed

Article View: comp.lang.postscript

Article #1630

Back to comp.lang.postscript Previous Next

#1630

From: Bill Silvert
Date: Wed, 24 Jan 1990 14:25

16 lines
1210 bytes

I'm a novice PS programmer who is stuck with having to carry my disks to
a shared machine which is networked to a PS printer by the parallel port.
This means that I don't get any diagnostics back from bad programs, they
just vanish.  Even when I run PS on a machine with feedback through the
serial port the messages are really cryptic, such as telling me that
there is no string on the stack without letting me know where in the
program the problem arose.  Getting interactive access to a machine
appears to be impossible.

Are there any techniques for sending a PS file to a machine and getting
useful debug info printed?
-- 
Bill Silvert, Habitat Ecology Division.
Bedford Institute of Oceanography, Dartmouth, NS, Canada B2Y 4A2
UUCP: ...!{uunet,watmath}!dalcs!biomel!bill
Internet: bill%biomel@cs.dal.CA		BITNET: bill%biomel%dalcs@dalac

Technical Details

Message-ID: <1990Jan24.142545.24543@cs.dal.ca>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.dal.ca!silvert

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.dal.ca!silvert
From: silvert@cs.dal.ca (Bill Silvert)
Newsgroups: comp.lang.postscript
Subject: Debugging advice needed
Message-ID: <1990Jan24.142545.24543@cs.dal.ca>
Date: 24 Jan 90 14:25:45 GMT
Organization: Habitat Ecology Div., Bedford Inst. of Oceanography
Lines: 16