Bug 123475 - Editor view should provide better feedback when in function with no symbolic info
Summary: Editor view should provide better feedback when in function with no symbolic ...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-11 12:47 EST by John Cortell CLA
Modified: 2020-09-04 15:18 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Cortell CLA 2006-01-11 12:47:05 EST
If you select a frame in the Debug view that's associated with a function with no symbolics info, the editor view does not update. As such, it seems to the user that he is still at the location of the previously active frame. The editor view should update and display something to the effect of "No symbolics info available", much like there is a "Source not found" editor window that comes up when the frame's source file cannot be found by the debugger.

To reproduce the problem, create a simple Cygwin/CDT projects that has a printf(). Launch a debug session and switch the stepping to instruction-mode. Then step into the printf(). You will see that the editor window remains as it was when the current PC was in main().

Note that this particular report is distinct from 81353 in that it is not concerned with getting the disassembler view to automatically display. This report simply states that the *editor* view should reflect that source-level debugging is not available when stepping/stopping in a function that has no symbolics info. Now, if diassembly display is somehow integrated into the editor view/pane, then indeed both bug reports will be resolved at that point.

Also, note that there is an important distinction between a function whose source cannot be found, and a function that has no symbolics info. This bug report is concerned with the latter, as current behavior for the former is not problematic.