| Title: | "OSF/Motif" is a trademark |
| Notice: | MOTIF kit note in 7.* |
| Moderator: | GOOEY::GRASS |
| Created: | Mon Aug 07 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5973 |
| Total number of notes: | 24620 |
Hi,
a customer has a very strange problem. He has VMS 6.1 and MOTIF 1.2-3.
He has a Local Area Vaxcluster with one Alpha 2100 which has the system
disk and 4 Alphastations, which have no system disk.
If he does:
$for/debugger kk
$link/debugger kk
$run/debugger kk
from any of the alphastations this works correctly, but if he executes
those commands in the main Alpha 2100 the following error appears:
X Toolkit Warning: Urm__CW_ConvertValue: Couldn't convert identifier
'src_file_un_pbident' - MrmNOT_FOUND
X Toolkit Warning: Urm__CW_ConvertValue: Couldn't convert identifier
'src_file_un_pbident' - MrmNOT_FOUND
%DEBUG-E-DBGERR, internal debugger coding error
-DEBUG-F-FATALSTATUS, a fatal condition was detected by the debugger.
%DEBUG-F-INITERR, an error has occurred during debugger initiliziation,
unable to continue this session.
Interrupt
I suppose there is a configuration missing or something like that, but
don't know where to look for troubleshooting info.
Any help would be appreciated.
Nieves
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5956.1 | GRIM::MESSENGER | Bob Messenger | Tue Apr 22 1997 17:37 | 4 | |
What happens if they use the character cell interface to the debugger, i.e. define dbg$decw$display " " before running the kk image? -- Bob | |||||
| 5956.2 | access violation | MDR01::NIEVES | MCS Madrid | Wed Apr 23 1997 13:13 | 35 |
Hi,
this is the result of doing the
$define dbg$decw$display " " before running the kk image.
*********************************************************
$ define dbg$decw$display " "
$ for/deb kk2
%FORT-I-DBGOPT, THE NCOPTIMIZE QUALIFIER IS RECOMMENDED WITH DEBUG
QUALIFIER
$ lin/deb kk2
$ run/deb kk2
OpenVMS AXP DEBUG Version V1.5-001
%DEBUG-I-INITIAL, language is FORTRAN, module set to KK2$MAIN
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual
address=000000F8, PC=00189AA4, PS=0000001B
Improperly handled condition, image exit forced.
Signal arguments ....
Register dump
****************************************************************
The customer doesn't know which Fortran version he is using, I wonder
if this has something to do with version incompatibility.
Any clues?
Nieves
| |||||
| 5956.3 | fortran 90 | MDR01::NIEVES | MCS Madrid | Thu Apr 24 1997 05:06 | 8 |
Hi,
they have Fortran 90 V2.0. I think this is compatible with his VMS
version, then what could be the problem??
Regards,
NIevese
| |||||
| 5956.4 | GRIM::MESSENGER | Bob Messenger | Mon Apr 28 1997 10:34 | 8 | |
It's interesting that they're running V6.1 but the debugger says it's V1.5. Make sure they don't have any .exe files in sys$specific:[sysexe] or sys$specific:[syslib]. If the debugger is accvio'ing before it gets to the DBG> prompt then this sounds like a debugger problem rather than a DECwindows problem. -- Bob | |||||