[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

194.0. "DECwindows and the debugger" by STAR::ANDRE (Andr� J. St. Laurent) Tue Feb 14 1989 08:56

   I have SDC VMS V5.1 and DECwindows V5.1 installed on a standalone �VAX-2000.
When I compile and link programs (either in BLISS and in BASIC) and attempt to
run them, I get the following error message, which I think is bizzare to say the
least:

$ r test
Error activating image DUA0:[SYS0.SYSCOMMON.][SYSLIB]UISSHR.EXE;
File not found
Cannot access the main debugger
$        

   But, I'm NOT using UIS any longer; WINDOW_SYSTEM is set appropriately etc,
there are no UIS logicals defined and my debugger initialization file has no
UIS-related references in it.  Anybody know what's going on here?

   BTW, copying UISSHR.EXE from some other system to SYS$SHARE solves this
problem, however another crops up.  I have the SPAWN command bound to a key.
When I bop that key I get:

	Spawn command failed
	Internal debugger error detected
	File not found

   WHAT file not found?  These problems never occurred with UIS.

	Thanks, Andr�

P.S.  The compile and link commands are as follows:

	$ BLISS /DEB TEST
	$ LINK  /DEB TEST, DECW.OPT/OPT
	$
	$ TY DECW.OPT
	SYS$LIBRARY:DECW$DWTLIBSHR              /SHARE
	SYS$LIBRARY:DECW$XLIBSHR                /SHARE
	SYS$LIBRARY:DECW$TRANSPORT_COMMON       /SHARE
T.RTitleUserPersonal
Name		DateLines
194.1UISSHR comes with VMS, not with VWSAGBEAR::HORNERA.G.Bear, Low tech teddy bearTue Feb 14 1989 09:138
    With regard to the UISSHR.EXE file, it comes with VMS, not with VWS.  I
    suspect that your VAXstation used to have VWS on it, and someone got a
    little overzealous when housecleaning.  I'm not sure why the debugger
    went looking for it, but since it is a VMS supplied file, the debugger
    has every right to expect that its there.

               Dave
194.2What I've learned about UISSHR...WAYLAY::GORDONThe shimmer of distance...Tue Feb 14 1989 09:5019
    	VMS ships with a set of stub routines for UIS (and CDD, and
    probably some other things I don't know about.)  UIS$PRESENT at
    least, is one that is assumed to be available by a fair amount of
    software.  If you install VWS, it replaces the stub routines with
    real routines.
    
    	The debugger uses UISSHR initially to see if it should fire
    up another window for your output. [simplification]
    
    	UISSHR.EXE must be INSTALLed if you want to ANALYZE/PROCESS
    image dumps for images installed with privileges, or linked against
    protected images. [This had me going for a while...]
    
    	[Disclaimer:  I have nothing to do with VMS, VWS, or the Debugger
    groups, and all of this material was gleaned from Notes at one time
    or another.]
    
    						--Doug
194.3Debugger does look at UISSHRVIRRUS::DIEWALDWindows and murders and orcs, oh my!Wed Feb 15 1989 14:067
.1 and .2 are correct.  The Debugger needs UISSHR, even on a DECwindows
system, even if the routines are only stubs.  UISSHR should be on your
system as part of VMS.

							Jeff Diewald
							VAX Debugger