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

Conference turris::decladebug

Title:Digital Ladebug debugger
Moderator:TLE::LUCIA
Created:Fri Feb 28 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:969
Total number of notes:3959

831.0. "Even more MONITOR VIEW woes" by ADA9X::BRETT () Tue Feb 11 1997 09:50

dxladebug 4.0-29

(ladebug) p ((a_scope_ptr)0x14049880)->using_decls
0x0

(ladebug) $ monitor ((a_scope_ptr)0x14049880)->using_decls

The MONITOR Value/Assign shows "a_using_decl_ptr"


T.RTitleUserPersonal
Name
DateLines
831.1CXXC::MJHANSMatthew Hanselman, DEC CTue Feb 11 1997 10:3936
I've run in to this as well.

Problem is, it sometimes works.

works:  Use the program at the bottom.  Putting a monitor on
	((a_scope_ptr) <memory address)->variables 
	will yield a correct memory address

doesn't work: Use /usr/proj/decc2/mainline/exxalphaosf/bl36/exe/exx, stop in
lower_scope, and do the same.  The monitor's "value" will read "a_variable_ptr".
 Attempting to print the same value will give a correct memory address.

								- Matt

struct a_variable;
struct a_scope;

typedef a_variable* a_variable_ptr;
typedef a_scope* a_scope_ptr;

struct a_variable {
  a_variable_ptr next;
};

struct a_scope {
  a_variable_ptr variables;
};

main()
{
  a_scope_ptr scope = new a_scope;
  scope->variables = new a_variable;
  scope->variables->next = 0;

  return 0;
}
831.2TLE::MURRAYWanfang MurrayMon Feb 24 1997 10:244
See reply on 833.1

Wanfang