Re: Problem with debugger & based data structures

[Rich Duzenbury <rduz-midrange@xxxxxxxxxxxxxxxxxxx>]

At 06:47 PM 6/10/03, you wrote:
> Looks interesting.
> Does it matter what the variable is named? Is it actually called
> "stuff" in your original code or is that just an example name?

No, it's not really called 'stuff' in the original code.  I needed to make 
a stripped down example for posting to the list.  Just for fun, I changed 
the variable in the function to be called stuff_in, but have the same problem:

 **************************************************************************
 * Run a test...
 **************************************************************************

P test            b
D test            pi              n
D  stuff_in                           likeds(stuff_t)

D result          s               n
 /free
    stuff_in.alpha = 'Hello, World';
    stuff_in.unsigned = 1;
    return *on;       // Breakpoint 2 here
 /end-free
P test            e

If I try to eval stuff_in at breakpoint number 2, I get 'Identifier not 
found'.  I also tried %var(stuff_in), no success either.

Thank you for any further suggestions you may be able to offer.



> The reason I say that is because I had an issue with fields named
> "qual". They would not work with the debugger.
> To view them I had to use the %var(qual) built-in function in the
> debugger.  e.g.:
>
>    eval  %var(stuff)
>
> -Bob Cozzi

Regards,
Rich