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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2313.0. "DW DEBUG Error When Examine String" by CSC32::DUBOIS (The early bird gets worms) Tue Feb 20 1990 13:58

With the DECWindows debugger, we get the following error when trying to 
EXAMINE a string:

%DEBUG-F-INTMEMERR, internal memory-pool error
-LIB-F-BADBLOADR, bad block address

Running the short C program below, compiled and linked /DEBUG, I step through
to the printf.  I then click on the DATA menu and VARIABLES, on the EXAMINE
(variables), I type the variable to examine as STR[0:4].  It then gives the
error.  After that I was not able to regain control of any of the DEBUGGER
windows.

Can someone please tell me why this is happening, and if there is anything
we can do to get around it?

    Thanks,

           Carol duBois

**************************************

main()
{
char *str="a crash";
printf("%s",str);
}
T.RTitleUserPersonal
Name
DateLines
2313.1QUARK::LIONELFree advice is worth every centTue Feb 20 1990 15:066
I suggest you ask this in TURRIS::DEBUG.  Press KP7 to add it to your
notebook.  (Or, alternately:

	ADD ENTRY DEBUG /OBJECT=easynote.confs.basesys.debug

if you have DNS support.)
2313.2Internal Memory ErrorCSC32::DUBOISThe early bird gets wormsThu Feb 22 1990 12:4510
<I suggest you ask this in TURRIS::DEBUG.  

Thanks, Steve, I have already put this in the DEBUG notesfile, but have not
received any response (note 781.0).  This is specific to DECWindows, so I
was hoping someone in here might have some ideas about it.  It does not
happen in the regular DEBUGGER.

Has anyone heard of this before?

        Carol
2313.3QUARK::LIONELFree advice is worth every centThu Feb 22 1990 13:087
It's still the debugger.  That they use a DECwindows interface is not
directly relevant.

If you get no response, I suggest a QAR against the debugger using the
databases on TRIFID.

				Steve
2313.4CSC32::DUBOISThe early bird gets wormsFri Feb 23 1990 13:463
Thanks, Steve.

      Carol