Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU
Newsgroups: comp.os.vms
Subject: VAX DEBUG v4.7-1 bug
Message-ID: <880808235903.120@CitHex.Caltech.Edu>
Date: 9 Aug 88 06:59:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 13

I've narrowed down the problem  I  reported  earlier  with  the  debugger  not
dealing properly with zero-terminated ASCII strings when debugging C programs.
The problem occurs when using VAX DEBUG version 4.7-1, but not when using  the
DEBUG  version  4.5-6.   The  problem  occurs whether VAX C version 2.1-007 or
version 2.3-024 is used, and appears not to depend on any other of the  system
shareable  libraries.   The workaround, therefore, is to copy the old versions
of SYS$LIBRARY:DEBUG.EXE and SYS$MESSAGE:DBGTBKMSG.EXE onto your  system,  and
then define DEBUG and DBGTBKMSG to point to them (for example:
        $ DEFINE DEBUG SYS$SHARE:DEBUG_V045-6
        $ DEFINE DBGTBKMSG SYS$MESSAGE:DBGTBKMSG_V045-6
is what I've set up for myself on CITHEX) when you  need  to  debug  something
that  uses a lot of ASCIZ.  Now that I've narrowed the problem down to "almost
certainly a VAX DEBUG bug introduced between v4.5-6 and v4.7-1",  can  anybody
tell me if this is still a problem under VMS v5.0?  Thanks.