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

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

353.0. "Errors with debugger" by MDR01::JMGUERRA (MCS Madrid) Thu Mar 20 1997 04:09

Hi,

A client has encounter the following errors using the grafic debugger of
POSIX 3.0D:

%DEBUG-I-CANTCREATEMAIN
-LIB-F-NOCLI
-DEBUG-I-SHRPRC
-DEBUG-W-DWNOT1PROC

The client has Alpha OpenVMS 7.1, Motif 1.2-4, and POSIX.  This only
happens whe usin the grafic debugger of POSIX.  If they use the Motif 
debugger, everything works fine.

Please, Do you know of some retrictions?  Are this products compatible?
If any have seen these errors before, can you gave us any clue to look
for?

Thanks in advance
Jose MIguel

PD: Crosposted in DECWINDOWS, POSIX and VMSNOTES
T.RTitleUserPersonal
Name
DateLines
353.1Wrong ConferenceXDELTA::HOFFMANSteve, OpenVMS EngineeringThu Mar 20 1997 09:127
:PD: Crosposted in DECWINDOWS, POSIX and VMSNOTES

    If this is the standard debugger, use the debugger notes conference.
    If this is a POSIX-private debugger, then the POSIX conference is the
    place to go.  And based solely on the error messages, this looks like
    the standard OpenVMS debugger.

353.2AUSS::GARSONDECcharity Program OfficeThu Mar 20 1997 16:5410
    re .0
    
    It looks as if the standard debugger is trying to SPAWN the debug
    "control" process (for want of a better term) and the spawn is failing
    because the CLI isn't there. This can occur if the image being debugged
    is run directly in a subprocess (or detached process) which I can imagine
    could occur in the POSIX environment (without your being aware of it).
    
    I would try the POSIX and DEBUG notes conferences for other notes that
    might describe this problem.