Bug 92574 - Do not ghost step upon invalid stack frame
Summary: Do not ghost step upon invalid stack frame
Status: RESOLVED DUPLICATE of bug 86676
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:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-25 09:32 EDT by Oyvind Harboe CLA
Modified: 2005-05-06 18:28 EDT (History)
0 users

See Also:

Attachments
Examples of error messages in evaluating the stack frame (1.69 KB, text/plain)
2005-04-25 09:36 EDT, Oyvind Harboe CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oyvind Harboe CLA 2005-04-25 09:32:02 EDT 
"Step/step into" should not be ghosted upon invalid stack frames.

When certain CPU's boot, their stack pointer points to the first address
*beyond* the RAM.

E.g. if the range of valid RAM is in the range 0x000000-0xffffff, then SP will,
upon reset, point to 0x1000000. 

If I enter "step" in the GDB console, I eventually leave the area where GDB will
fail to evaluate the stack frame and CDT resumes normal operation.

Øyvind
Comment 1 Oyvind Harboe CLA 2005-04-25 09:36:12 EDT 
Created attachment 20299 [details]
Examples of error messages in evaluating the stack frame

Despite such error messgaes in evaluating the stack frame, the step, resume,
etc. must available.
Comment 2 Nobody - feel free to take it CLA 2005-05-06 18:28:29 EDT 

*** This bug has been marked as a duplicate of 86676 ***