Dumb DECWindows Debugger Question.

Thread View: vmsnet.misc

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Dick Munroe Tue, 29 Sep 1992 11:14

#136

Author: Dick Munroe
Date: Tue, 29 Sep 1992 11:14

68 lines
2657 bytes

I'm stumped.  I'm trying to get the DECWindows Debugger to come up from another
account (other than my primary one).  I have security set as follows:

DECNET HULK SYSTEM
DECNET HULK MUNROE
DECNET HULK DMC$INFO
DECNET HULK NEWSMGR

When ever I attempt to run a debugging session from NEWSMGR I get:

$ run/debug user1:[munroe.toolshed.news-to-notes.exe]out-to-isvnet.exe
XIO:  unable to open connection WSA1:
      after 0 requests (0 known processed) with 0 events remaining.
%XLIB-F-IOERROR, xlib io error
-DECW-E-CNXABORT, connection aborted
%DEBUG-F-FAILXTINIT, the debugger detected an error when trying to connect to
the DECWindow software.
-DEBUG-F-FATALSTATUS, a fatal condition was detected by the debugger.
%DEBUG-F-INITERR, an error has occurred during debugger initialization, unable
to continue this session.

Which I have always associated with a security problem.

The debugging logicals defined for the account are:

$ SHO LOG DBG*

(LNM$PROCESS_TABLE)

(LNM$JOB_807A4C80)

(LNM$GROUP_000201)

(LNM$SYSTEM_TABLE)

  "DBG$INPUT" = "SYS$INPUT:"
  "DBG$OUTPUT" = "SYS$OUTPUT:"

(DECW$LOGICAL_NAMES)

I've poured over TFM and tried various things like the following:

$ set display/create
$ set display/node=hulk
$ run/debug user1:[munroe.toolshed.news-to-notes.exe]out-to-isvnet.exe
Xlib:  connection to "HULK::0.0" refused by server
Xlib:  Client is not authorized to access server
X Toolkit Error: Can't Open display
%DWT-F-DWTABORT, xtoolkit fatal error
%DEBUG-F-FAILXTINIT, the debugger detected an error when trying to connect to
the DECWindow software.
-DEBUG-F-FATALSTATUS, a fatal condition was detected by the debugger.
%DEBUG-F-INITERR, an error has occurred during debugger initialization, unable
to continue this session.

Which would seem to indicate a security problem, which gets back to the setting
of the security information, which looks good to me.  Where is the DECWindows
security data base kept?

Can someone explain what's going on here?  I know I've done this before but I
simply CAN'T remember how right now.
-- 
Dick Munroe				Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroe
267 Cox St.				Office: (508) 568-1618
Hudson, Ma.				FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.

Re: Dumb DECWindows Debugger Question.

#138

Author: Dick Munroe
Date: Tue, 29 Sep 1992 15:59

50 lines
2280 bytes

Well, Harry Flowers suggested the following;

>>I'm stumped.  I'm trying to get the DECWindows Debugger to come up from another
>>account (other than my primary one).  I have security set as follows:
>>
>>DECNET HULK SYSTEM
>>DECNET HULK MUNROE
>>DECNET HULK DMC$INFO
>>DECNET HULK NEWSMGR
>
>Can you connect from HULK from another account?  When I've had this problem,
>it was because I hadn't defined the node in NCP on the workstation.  If
>HULK::MUNROE works and HULK::NEWSMGR doesn't (and you don't have *::MUNROE
>in there somewhere), then you've got me stumped.
>
>$ MCR NCP SHOW NODE HULK ! Should show you node HULK
>
>If it was defined, but not SET, you can do a NCP> SET NODE HULK ALL
>

The ncp database defines HULK as:

Node Volatile Summary as of 29-SEP-1992 11:51:43

Executor node = 1.1 (HULK)

State                    = on
Identification           = DECnet-VAX V5.4-1,  VMS V5.4-2

The SCS node name is HULK and the SCS system is 1025 (which from my tribal
recollection is correct (area*1024+decimal = DECNET NODE NUMBER)

I tried adjusting the protections on the various SYS$SYSTEM:NET*.DAT
files with no effect (as expected).  I also tried replacing the HULK
designation by 1025 (the decnet node number) with no joy.

I CAN get it to work by using *::NEWSMGR in the security settings (or *::*)
which works for me (in my shop, security isn't an issue), but I'm still
immensely puzzled by why the checking for the node is messing up.  I have to
assume that it has SOMETHING to do with the way DECnet/DECWindows is
configured, but what in the world it could be is a really question.

Still stumped, but making progress.
-- 
Dick Munroe				Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroe
267 Cox St.				Office: (508) 568-1618
Hudson, Ma.				FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.

Re: Dumb DECWindows Debugger Question.

#152

Author: Harry Flowers
Date: Thu, 01 Oct 1992 23:59

21 lines
1191 bytes

In article <1992Sep29.115928.4593@dmc.com>, munroe@dmc.com (Dick Munroe) writes:
>>>I'm stumped.  I'm trying to get the DECWindows Debugger to come up from another
>>>account (other than my primary one).  I have security set as follows:
>>>
>>>DECNET HULK SYSTEM
>>>DECNET HULK MUNROE
>>>DECNET HULK DMC$INFO
>>>DECNET HULK NEWSMGR

Since HULK was also the node where he was running the programs, you
can't use the node name for some reason.  It should work just fine
if you use zero for the system (works for my VAXstation):

DECNET 0 SYSTEM
DECNET 0 MUNROE
DECNET 0 DMC$INFO
DECNET 0 NEWSMGR

--
Harry Flowers                           Internet: FLOWERS@MEMSTVX1.MEMST.EDU
Memphis State University                & Bitnet: FLOWERS@MEMSTVX1

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads