Problems
- In the range table based dwarf2-Stack analyse may be signals (if we are running under a UNIX) ...
Under minimal L4, we don't have this mechanism.
But at runtime, newer a signal-frame will be found, thus only
compiling Problems remains
Start-code
A few frame table entries must be called in crtbegin.o
When linking a linux-Programm -static, in frame_dummy fe function
__register_frame_info_bases in unwind-dw2-fde.c is called.
( objdump -D -l -j .text exceptiontest.lnx)
Thread specific storage
The unwind-sjlj.c needs Thread specific storage, the others not.
Perhaps the dwarf-Based method needs less context-Management
In eh_globals.cc the thread specific storage implemented by an an hoc mechanismen with a static storage
Section .gxx_except_table
With objdump -h exception.lnx we see a calaculated exception-Table . - both in the linux-exe and in the L4-exe
We see it also in the assember-output.