Conference turris::decladebug

820.0. "Source pointer arrow sometimes incorrect when navigating scopes" by CXXC::MJHANS (Matthew Hanselman, DEC C) Fri Feb 07 1997 11:09

Admittedly a minor gripe, but I'd love to see it:

dxladebug's source correlation relies too heavily upon the instruction level. 
The case in point is when you attempt to navigate across scopes.  In the source
attached, step into the first call of function a().  Since this call is 1
instruction (a bsr), ladebug considers this instruction executed.  If you move
the scope from a() to main(), you'll notice that the source arrow is now
pointing to the return, rather than to a().  Note that if you omit the "static"
keyword, the call is now 4 instructions long (all of which have not been
executed), so ladebug will correctly point to a() if you move the scope.

Note that xdbx is doing something that allows it to get it correct.

This minor detail puts uneccesary strain on the programmer attempting to trace
a function through the several scopes, esp when they are all static.  To be
useful, you have to combine both the arrow and the name in the scope box.  It
can get really confusing if you have two calls to a() right after each other.

								- Matt

static int a()
{
  return 5;
}

main()
{
  int f;

  a();

  return 5;
}

We will look into this.

Wanfang