IJAH400@INDYVAX.BITNET (07/07/88)
<>>This is interesting-- I got an error message while running a Pascal
<>>program of doubtful soundness inside the debugger. The error is supposed
<>>to have been recorded in the debug error log,DBGERR.LOG and the following
<>>dump was displayed:
<>>
<>>The base address of DEBUG is 00018800
<>> module name routine name line rel PC abs PC
<>> SHARE$DEBUG 00000000 0001919A
<>
<> Unfortunately, he has since modified the program to fix it, but
<>I could always try to load the original from backup if necessary. My
<>question is, is it normal for the debugger to blow up like this?
<
<One of our users have hade the same problem, and I don't know what cause the
<problem. The user also modified the program to fix the problem. I don't think
<that this behaviour is normal for the debugger (correct me if I'm wrong).
<Maybe an SPR should be sent to Digital??
Yeah. And your chances for getting a quick answer will improve if you:
(1) Include source, object and exe of the program that causes the problem,
with data, and how to reproduce the problem (preferably a command procedure,
I usually provide one if it takes more than two or three commands to show
the problem), (3) you can provide a smaller program that reproduces the
problem it might help them out (get you an answer faster), and (2) version
numbers for everything involved (for example, VAX/VMS and the Pascal
compiler). Surprising how often people forget to include all these details.
If you are on DSIN (Digital Software Information Network, there's some
European equivalent also, but I can't remember the acronym) you can enter an
SPR (or just a "problem report") right there. I've had very good turnaround
time that way. Also, they'll get the stuff right off your machine if you
want them to (we had them download source for a home-grown print symbiont
that demonstrated a problem that way once). It's cheaper and faster than
sending them a tape...
Jim Harvey
IJAH400@INDYVAX (BITNET) or IJAH400%IVAX.DECNET@GOLD.BACS.INDIANA.EDU