[haiku-bugs] Re: [Haiku] #10459: [Debugger] Investigate anomalous single stepping behavior

  • From: "anevilyak" <trac@xxxxxxxxxxxx>
  • Date: Fri, 24 Jan 2014 00:19:45 -0000

#10459: [Debugger] Investigate anomalous single stepping behavior
-------------------------------------+----------------------------
   Reporter:  anevilyak              |      Owner:  anevilyak
       Type:  bug                    |     Status:  closed
   Priority:  normal                 |  Milestone:  R1
  Component:  Applications/Debugger  |    Version:  R1/Development
 Resolution:  no change required     |   Keywords:
 Blocked By:                         |   Blocking:
Has a Patch:  0                      |   Platform:  All
-------------------------------------+----------------------------
Changes (by anevilyak):

 * status:  new => closed
 * resolution:   => no change required


Comment:

 After digging a bit further, I'm forced to conclude that this is indeed
 simply a quirk of the line number program in question. Both objdump and
 our state machine agree that line 21 (aka "return 5") spans range
 0x8f2-0x917, unrelocated. As you pointed out, 0x903 is the starting point
 of the object destructor + epilogue, aka in the middle of the
 aforementioned statement, and that is in fact precisely the address we
 wind up at after stepping over line 19. So yes, gcc has condensed that
 last return + destructor/epilogue into a single statement for debugging
 purposes, and there's unfortunately nothing we can really do to simplify
 the confusion there.

--
Ticket URL: <https://dev.haiku-os.org/ticket/10459#comment:5>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: