[Libunwind-devel] Interest in .debug_frame support?

[Daniel Jacobowitz]

Corey Ashford asked in February whether there were any plans for
.debug_frame support.  I have a similar question - is there any
interest in including .debug_frame support?

I've been looking at a system where I'd like to have backtraces during
debugging (from memory allocation debuggers, et cetera).  This is a
debugging feature, so I'm willing to put extra data on the target
during it, probably using .gnu_debuglink to point at separate files.
But the overhead of .eh_frame is not acceptable.

The things that would have to be implemented:

  - Finding and opening files to map .debug_frame.

  - Handling the differences between .debug_frame and .eh_frame.
  They're important but small.

Libunwind seems like the most sensible way to do this.  .debug_frame
is similar enough to .eh_frame that all the necessary interfaces are
already present.

-- 
Daniel Jacobowitz
CodeSourcery