On Tue, Apr 25, 2006 at 03:37:04AM +0100, Derek Fawcus wrote: > > Well, this is to unwind trough exceptions through the C stack: > > There is no c++ code here, last I looked there is no c++ in dietlibc.
That's the beauty of a shared library -- you never know who might end up calling you, and if you have routines which do call back -- you never know what awaits you there as well. So, these days for a perfectly law-abiding pureC shared library which defines bar() (from my example) there must be a .eh_frame section to make C++ applications (the ones calling bar() by the virtue of dynamic linking) feel better. > Well I always find the .comment sections annoying, lots of junk saying > which version of gcc compiled a given module... Well, at least for those you can use mcs(1) but .eh_frame was made mandatory by the AMD64 ABI. Thanks, Roman.
