| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 601.1 | This DEBUG newer than 5.2-41S? | WJG::GUINEAU | | Thu Apr 27 1989 19:01 | 7 |
|
How does this compare to the version of DEBUG in VMS5.2-41S ?
Also, the BOOKREADER formatted files are protected.
John
|
| 601.2 | Window Mode? | OIWS19::WALTERS | | Thu May 04 1989 13:42 | 7 |
| Is there any logical or anythin I need to define to get debug to
come up in window mode. All I can get is the Terminal Mode...
Thanks,,
Brian.
|
| 601.3 | | QUARK::LIONEL | The dream is alive | Thu May 04 1989 15:42 | 5 |
| Do you have DECW$DISPLAY defined for your process? If you do, it will come
up in window mode (if you have the right version).
Steve
|
| 601.4 | And no DBG$DECW$DISPLAY " " | MRFLEX::MILLER | Bush For President...Kate Bush! | Thu May 04 1989 19:06 | 6 |
| Make sure somebody didn't disable it on you via system logical.
Regards,
== ken miller ==
|
| 601.5 | DEBUG doesn't like SYS$LIBRARY search list | NYMPH::ZACHWIEJA | Focusing my input | Fri May 05 1989 15:46 | 47 |
|
After installing this kit on our cluster, the debugger can nolonger
find DEBUGSHR.EXE when SYS$LIBRARY is defined as a search list.
It seems that it only translates the logical once, and looks for
the image in the location for the first translation.
In my process table I have SYS$SHARE defined as
$ DEFINE SYS$SHARE SIDE$:[UISCNV.OBJ], -
SYS$SYSROOT:[SYSLIB]
Again in my process table I have SYS$LIBRARY defined as
$ DEFINE SYS$LIBRARY MIGRESD$:[SYSLIB], -
VWSRESD$:[SYSLIB], -
RESD$:[SYSLIB], -
SYS$SYSROOT:[SYSLIB]
All of the logicals that you don't recognize are concealed
device specifications.
If I say DIR SYS$LIBRARY:DEBUGSHR.EXE I get
Directory SYS$COMMON:[SYSLIB]
DEBUGSHR.EXE;2 1493/1494 12-APR-1989 07:44:12.46
Total of 1 file, 1493/1494 blocks.
If I say RUN PROGRAM where PROGRAM.EXE was linked /DEBUG I get
%DCL-W-ACTIMAGE, error activating image SIDE$:[SYSLIB]DEBUGSHR.EXE
-CLI-E-IMAGEFNF, image file not found _$1$DUA2:[ZACHWIEJA.RESD.][SYSLIB]DEBUGSHR.EXE;
My guess is that it is doing something really stupid like instead
of looking for the image in SYS$SHARE, it is looking in SYS$LIBRARY,
but not only that it seems that rather then just saying SYS$LIBRARY
it is doing a translation on SYS$LIBRARY and then looking for the
image symbol in the file DEBUGSHR.EXE in whatever directory comes
out of the translation.
If I deassign the search list definition for SYS$LIBRARY it works
just fine.
_sjz.
|
| 601.6 | Fixed in next release... | TLE::CARIGNAN | Don Carignan - VAX DEBUG & XDDEBUG | Mon May 08 1989 11:55 | 6 |
|
This is a known problem in the V5.2 debugger which will be fixed in a release
after 5.2. The workaround is to $ DEFINE DEBUGSHR SYS$SYSROOT:[SYSLIB]DEBUGSHR
- Don
|
| 601.7 | How about an internal release or patch | NYMPH::ZACHWIEJA | 85% or bust | Tue May 09 1989 15:30 | 15 |
|
The workaround was not difficult to figure out. I am just amazed
that such a piece of code would actually be released. Search lists
are pretty darn fundamental as is the use of SYS$SHARE. How could
we possibly mess this up. And how did it get through SQM ? And how
did it go unnoticed during development ? Maybe there is some higher
reasoning that I am just not seeing ?
Almost every programmer uses the debugger. This is a major major
bug despite the workaround. I think an internal release would well
worth the extra effort. It doesn't occur to most people to look
into the DECwindows notesfile because the debugger doesn't work.
_sjz.
|
| 601.8 | | PSW::WINALSKI | Paul S. Winalski | Tue May 09 1989 16:19 | 9 |
| RE: .7
C'mon, be real. This is hardly a "major, major bug." The only way you can
encounter it is if you redefine SYS$LIBRARY and/or SYS$SHARE. How many people
outside the VMS group go around doing that? I'm not even sure we support
customers doing that.
--PSW
|
| 601.9 | | LESLIE::LESLIE | Andy ��� Leslie, CSSE/VMS Europe | Wed May 10 1989 01:26 | 2 |
| We don't. Which won't prevent 'em doing it...
|
| 601.10 | | DSSDEV::BIBEAULT | Grizzly Bear | Fri Jun 23 1989 11:12 | 5 |
| By the way, where is the debug conference? I've heard it mentioned, but
it's not listed in the related conference topic...
-mike
|
| 601.11 | TURRIS::DEBUG | TLE::CARIGNAN | Don Carignan - VAX DEBUG & XDDEBUG | Fri Jun 23 1989 12:47 | 6 |
| > By the way, where is the debug conference?
TURRIS::DEBUG
- Don
|
| 601.12 | DECwindows Debugger documentation? | PEACHS::GILBERT | Jeff Gilbert, VMS workstations support, CSC/AT | Tue Apr 17 1990 18:52 | 9 |
| I just did a dir of TLE::DEBUG$KIT:*.ps/size and found ~ 20,000 blocks of
documentation on the DECwindows debugger. Do we offer a hardcopy document
for the DW debugger that is available to customers other than bookreader?
Also, is this a supported product and if so, who supports it. (it might be
me :-)
Thanks,
Jeff
|
| 601.13 | | PSW::WINALSKI | Careful with that VAX, Eugene | Tue Apr 17 1990 18:56 | 4 |
| DECwindows Debugger on VMS is developed by the same team that does VAX DEBUG.
I suggest asking about support in the TURRIS::DEBUG conference.
--PSW
|
| 601.14 | | QUARK::LIONEL | Free advice is worth every cent | Wed Apr 18 1990 11:00 | 4 |
| And it's a part of VMS. You get it automatically when you're on a
workstation (unless you have defined DBG$DECW$DISPLAY to be " ").
Steve
|