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

Conference turris::debug

Title:	DEBUG
Notice:	Updated locations for reporting QARs -- see note 834.1
Moderator:	LOWFAT::DIETER

Created:	Fri Jan 24 1986
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1868
Total number of notes:	8200

1854.0. "Alpha DEBUG V7.1C fails w DEBUG/KEEP %DEBUG-E-INTERR" by CSC32::D_SANFORD () Tue Apr 08 1997 15:17

    OpenVMS Alpha DEBUG Version V7.1C-000, OpenVMS ALpha V6.2

    After setting up DEBUG V7.1, using DEBUG/KEEP does not work.  It
    looked like a problem with logcial names in SYSTEM (supervisor) .vs.
    (executive) tables, but it didn't matter.  What is strange is that
    DEBUG V6.2 comes up with DEBUG/KEEP.

    Customer claims that the DEBUGGER will ACCVIO on his system with
    DEBUG/KEEP, I could not duplicate this.  Also when he runs in 
    DECwindows mode, the keypad keys don't have any effect (e.g. KP0
    doesn't do a step, etc.).

    Regards, Drew Sanford
    C970313-973


    $ @sys$startup:debugsetup
    Please specify setup type; /JOB or /SYSTEM: /JOB
    Please specify debugger name; VMS or CXX or UNSET: CXX

    (LNM$SYSTEM_TABLE)

      "DEBUG" = "SYS$SHARE:CXXDEBUG.EXE"
      "DEBUGSHR" = "SYS$SHARE:CXXDEBUGSHR.EXE"
      "DEBUGUISHR" = "SYS$SHARE:CXXDEBUGUISHR.EXE"



    $ DEBUG/KEEP

             OpenVMS Alpha DEBUG Version V6.2-103R

    DBG> RUN TEST
    %DEBUG-E-INTERR, debugger error in DBGMRPC\DBG$WAIT_FOR_EVENT got a bad
     packet type or session corruption

T.R	Title	User	Date	Lines
1854.1	RUN DEBUGSHR	CUJO::SAMPSON	`Tue Apr 08 1997 23:08`	8
	Drew, After setting up the CXX debugger, instead of "DEBUG/KEEP", just say "RUN DEBUGSHR". The DCL command "hard-codes" the image name. I had a customer ask me the same question a while ago. HTH, Bob Sampson
1854.2		LOWFAT::DIETER	`Wed Apr 09 1997 09:45`	4
	exactly! Mary
1854.3	keypad not working with DECwindoes UI	CSC32::D_SANFORD	`Wed Apr 09 1997 14:49`	10
	Worked like a charm... There is a second problem in the base note, the keypad does not work using the DECwindows UI. It is as if the keypad is set to "NUMERIC", no "APPLICATION". He has file DECW$SYSTEM_DEFAULTS:VMSDEBUG.DAT, and this file appears to setup the keypad. If he goes back to the V6.2 debugger it works. He is using Motif V1.3, ECO 1. -drew
1854.4		LOWFAT::DIETER	`Wed Apr 09 1997 16:50`	22
	>There is a second problem in the base note, > the keypad does not work using the DECwindows UI. This is using the C++ debugger, correct? Did he follow these instructions, from the debugger kit install procedure and also in the C++ installation guide: * - On OpenVMS versions prior to V7.0, copy the following * resource file: * $ COPY DECW$SYSTEM_DEFAULTS:CXXVMSDEBUG.DAT - * DECW$SYSTEM_DEFAULTS:VMSDEBUG.DAT Actually, he probably wants to copy DECW$SYSTEM_DEFAULTS:CXXVMSDEBUG.DAT to his SYS$LOGIN, if not everyone on the system is using the C++ debugger. Also, he may have to switch between the two copies of VMSDEBUG.DAT (i.e. VMSDEBUG.DAT and CXXVMSDEBUG.DAT) depending on which debugger he is using at a given moment in time. Mary
1854.5	We just copied CXXVMSDEBUG.DAT to VMSDEBUG.DAT	CSC32::D_SANFORD	`Thu Apr 10 1997 13:21`	8
	Yes, C++. They did not follow this step, but claim they did read the installation guide/release notes. Too bad this is not better integrated, maybe DEBUGSETUP.COM can somehow detect a bad VMSDEBUG.DAT file? Something to think about if a new kit goes out. Looks like the customer if running now. -drew