Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!oakhill!nddsun1!axon!leivian
From: leivian@axon.sps.mot.com (Bob Leivian)
Newsgroups: comp.sys.next
Subject: How to you set a breakpoint to catch postscript errors
Message-ID: <1011@nddsun1.sps.mot.com>
Date: 29 May 91 17:51:33 GMT
Sender: root@nddsun1.sps.mot.com
Organization: Motorola PCRL, Tempe, AZ
Lines: 18

I am getting errors from the DPS client ... offending command blah
is printed into my terminal window but the program exits before telling
me which of the two hundred PSlineto commands in my code that
could have caused the problem.

I set a break point at 'exit' but the call stack has already been cleared
(problably by a longjmp or something)
and all I get is the DPS exection handler called from application 'run'

It would be real nice to know which of the 60,000 lines of user code 
caused the problem. Is there a place to intercept DPS client errors
while the user call stack is still intact?

--Bob L
-- 
Bob Leivian				leivian@email.pcrl.sps.mot.com
Neural Network Development Group	(602) 897-5117
2100 E. Elliot MD508			Tempe, AZ 85284