#12105 LOW Not Tri: OFW debugger renders ok prompt in the wrong place

[Zarro Boogs per Child]

#12105: OFW debugger renders ok prompt in the wrong place
-------------------------------------------+--------------------------------
           Reporter:  dsd                  |       Owner:  wmb at firmworks.com
               Type:  defect               |      Status:  assigned         
           Priority:  low                  |   Milestone:  Not Triaged      
          Component:  ofw - open firmware  |     Version:  not specified    
         Resolution:                       |    Keywords:                   
        Next_action:  never set            |    Verified:  0                
Deployment_affected:                       |   Blockedby:                   
           Blocking:                       |  
-------------------------------------------+--------------------------------
Changes (by wmb at firmworks.com):

  * priority:  normal => low
  * status:  new => assigned


Comment:

 I have looked at this before and never quite managed to work out why it's
 happening.

 The 'l' (redisplay) command will redraw the debugger display, which
 usually manages to clean things up (except in extreme cases like #12104
 where the display is fundamentally confused).

 Another way to trigger a similar display-confusion problem is to use 'f',
 then type

   ok debug foo  resume

 where foo is in the call chain of the word you are debugging.  In this
 case, 'l' will fix things up.

-- 
Ticket URL: <http://dev.laptop.org/ticket/12105#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system