#8508: Various classes no longer appear to be resolving members with recent gcc upgrades -------------------------------------+---------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1/Development Resolution: fixed | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All -------------------------------------+---------------------------- Comment (by anevilyak): Replying to [comment:7 bonefish]: > Unless there's a good reason to do that -- like both sections containing different parts of the information -- I wouldn't do that. I wonder anyway why the .debug_frame is no longer correctly written. After all it is documented to contain the information. Have you read anything about this (e.g. in the changelog, some announcement, or discussion)? Or might this just be a bug? The only related discussion I've managed to find is this: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40521 -- Ticket URL: <http://dev.haiku-os.org/ticket/8508#comment:9> Haiku <http://dev.haiku-os.org> Haiku - the operating system.