Comment 4 for bug 889984

So given from the discussion in the other bug:
- you're using another debugger, so the discussion about GDB is not relevant
- you're statically linking in the libgcc helper in question, so installing debuginfo packages is not relevant

The only question is whether the static copy of libgcc.a your toolchain is using provides debug information.

However, I do not quite understand your last sentence. With GCC, if you ask for debug information, you will *always* get .debug_frame. If you strip debug info, it will always remove .debug_frame together with the other DWARF sections (.debug_info etc.). I do not see any (normal) way how you ever could end up with an object that has .debug_info but no .debug_frame ...

Can you run a "readelf -a" on the copy of libgcc.a you're using and provide the results (at least for the object containing the helper function in question)?