This is sources Bugzilla
Bugzilla Version 2.17.5
Bugzilla Bug 5888
  if the unwind fails, stop the step Last modified: 2008-10-21 21:40
     Query page      Enter new bug
Bug#: 5888   Hardware:   Reporter: Andrew Cagney <cagney@redhat.com>
Host: Target: Build:
Product:     Add CC:
Component:   Version:   CC:
Remove selected CCs
Status: NEW   Priority:  
Resolution:   Severity:  
Assigned To: Unassigned <frysk-bugzilla@sourceware.org>   Target Milestone:  
Summary:
Keywords:

Attachment Description Type Created Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 5888 depends on: Show dependency tree
Show dependency graph
Bug 5888 blocks: 5876

Additional Comments:


Leave as NEW 
Mark bug as waiting for feedback
Mark bug as suspended
Accept bug (change status to ASSIGNED)
Resolve bug, changing resolution to
Resolve bug, mark it as duplicate of bug #
Reassign bug to
Reassign bug to owner of selected component

View Bug Activity   |   Format For Printing


Description:   Last confirmed: 0000-00-00 00:00 Opened: 2008-03-05 17:24
When a problem with stepping is detected there are two choices:

-> try to keep going
+ sometimes the stepper recovers (making things look better than they are)
- sometimes it doesn't (instead program is stepped into the weeds making things
look buggy) -> no possible recovery

-> stop immediately and report problem
- can leave the program in strange locations (making things look more buggy than
they are) -> recovery is to "step -i"
+ can't over-step or run into the weeds

While it is possible to work-around a stepping engine that stops early, it is
difficult to work-around one that keeps running into the weeds.

     Query page      Enter new bug
Actions: New | Query | bug # | Reports | Requests   New Account | Log In