Need help while debugging!!

[Manesh Sasankan]

This was a continuation of my previous thread of how to set up the X-window. i was able to set up the X-window & realized that the problem lies in my source code.

So linked the image with /DEBUG parameter and started the image in Debug mode. i did some initial step commands, once it reached the function XtToolkitInitialize(), it brings the following error.
>>>>>>>>>>>>

DBG> step
%DEBUG-I-DSFMISMATCH, using I64V82$DKA0:[VMS$COMMON.SYSLIB]LIBRTL.DSF; but it does NOT appear to match with DISK$I64SYS:[VMS$COMMON.SYSLIB]LIBRTL.EXE;1
%DEBUG-I-DYNIMGSET, setting image LIBRTL
%DEBUG-I-DYNMODSET, setting module LIB$FIND_IMAGE
%DEBUG-I-DYNLNGSET, setting language BLISS
%DEBUG-W-UNAOPNSRC, unable to open source file $1$DGA2027:[LIBRTL_5.SRC]LIBFNDIMG.BLI;1
-RMS-F-DEV, error in device name or inappropriate device type for operation
%DEBUG-I-DYNIMGSET, setting image RS1WS
%DEBUG-I-DYNLNGSET, setting language C
stepped to STN\main\%LINE 42447 in THREAD 1
DBG>
<<<<<<<<<<
This XtToolkitInitialize() is defined in the SYS$COMMON:[000000.DECW$INCLUDE]INTRINSIC.H;1
header file.

After this debug error, once i finish a few step command, the whole thing hangs. A new pop up window appears with an acknowledge button and has following error(this is my application based)(For more info please refer the attachment)

Fatal: Error 406225122 in getting text of message for HLI error 406224986

& the debugger stops responding after clicking the button in the pop up window & displays the following:

%DEBUG-I-EXITSTATUS, is '%SYSTEM-S-NORMAL, normal successful completion'
%DEBUG-I-NOSOURCE, No source for address: 0000000000000000

Appreciate if anyone could comment on this!!!

Thanks
/Manesh

[John Gillings · Accepted solution]

Manesh,

DEBUG-I-EXITSTATUS means your program has deliberately exitted, and with success status - more than likely in response to the fatal error. The other DEBUG messages you've posted are benign, they're telling you that the source codes for OS components are unavailable - this is normal.

As you say, the error message is from your application, so there's not much I can say about its interpretation.

The "hang" in DEBUG is because your application is "running" (actually just waiting for a response in your dialog box). You can hit ^C or ^Y and then type DEBUG at the $ prompt to get DEBUG control. You can then use SHOW CALL and/or SHOW STACK to work out where you are in the application.

Alternatively, instead of STEP try STEP/INTO or SET BREAK to get into routines of interest. You need to have some idea of where your program has problems, and focus your attention on examining program flow at those places. Use SET BREAK to stop at particular routines or source lines, or SET WATCH to stop when a variable is written.