Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/Debugger/Evaluator ToolTips    [ Add a report in this area ]  
Report #:  6917   Status: Open
Tooltips symbol lookup doesn't follow selected callstack entry
Project:  C++BuilderX/BC++ 2005 Build #:  1.0.1.103
Version:    THK Submitted By:   Russell Hind
Report Type:  Basic functionality failure Date Reported:  1/14/2004 4:04:40 AM
Severity:    Commonly encountered problem Last Updated: 3/20/2012 2:24:39 AM
Platform:    All versions Internal Tracking #:   196261
Resolution: None (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
Using DBK and bcc32 toolset, the tooltips will only ever show variable values from the latest callstack entry.  Selected a previous callstack entry shows the correct local variables in the local variables window, but hovering over a variable that is present in the locals window produces a tooltip of undefined symbol message

The tooltip evaluator should check the currently seleted stack entry when looking for variable values, not just the latest stack entry.
Steps to Reproduce:
1. Create a console project (bcc32 toolset) with the following code

void b(void)
{
int c = 1000;
}

int main( int argc, char * argv[] )
{
int a = 123;
    b();
    return 0;
}

2. Put a breakpoint in function b on the int c = 1000; line.  
3. Debug the project - it should stop in function b
4. Hover the mouse over c and a tooltip will be shown for c
5. Hover over a in function main and it will say undefined symbol.  This is correct as there is currently no local variable called a
6  In the threads/callstack window, select the 'main' entry
7. a is now shown in the locals window, but hovering over it sill shows 'undefined symbol' even though it is now available in the selected stack entry
Workarounds
None
Attachment
None
Comments

None

Server Response from: ETNACODE01