[haiku-bugs] Re: [Haiku] #8508: Various classes no longer appear to be resolving members with recent gcc upgrades

  • From: "anevilyak" <trac@xxxxxxxxxxxx>
  • Date: Wed, 11 Jul 2012 01:13:52 -0000

#8508: Various classes no longer appear to be resolving members with recent gcc
upgrades
-------------------------------------+----------------------------
   Reporter:  anevilyak              |      Owner:  anevilyak
       Type:  bug                    |     Status:  reopened
   Priority:  normal                 |  Milestone:  R1
  Component:  Applications/Debugger  |    Version:  R1/Development
 Resolution:                         |   Keywords:
 Blocked By:                         |   Blocking:
Has a Patch:  0                      |   Platform:  All
-------------------------------------+----------------------------
Changes (by anevilyak):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 The heuristic I added is apparently not quite correct either. I sometimes
 wind up with libraries where .debug_frame is several times larger than
 .eh_frame but the appropriate FDE/CIE are contained in the eh_frame
 section instead. I've checked out the git clone of gdb's latest source to
 see how they handle it, and their methodology is simply to try both
 sections in order, preferring .debug_frame first, and trying .eh_frame if
 it's not found in the former. Should I simply adapt us to do likewise,
 since it seems this is the only sane way to cope with the changing whims
 of the gcc developers?

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/8508#comment:10>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: