Hi,   I think that we had the same or a similar problem in the past. It showed up when we linked the libc to our program.   For a start, we then used the ddekit instead of the libc, because it offered some similar functionality. I'm not sure if we finally fixed it or not, but maybe this is a useful point to start your investigation.   Cheers   Sven   -- Sven Fülster

Steffen Liebergeld <steffen@...37...> hat am 21. Mai 2010 um 10:57 geschrieben:

Hello Genoders,

I'm having troubles with the C++ exception mechanism:

In base/src/platform/_main.cc:_main(), the exception frames are set up in function init_exeption_handling(). Unfortunately, during startup of the init task, this runs into a null pointer. I could trace this back to base/src/base/cxx/exception.cc:__register_frame(__eh_frame_start), which obviously calls some gcc-provided function. I am using the toolchain you provide on your website. Did you have similar experiences during your development? Do you have an idea what is going wrong in my setup? Where should I start my investigations?

Many thanks in advance, Steffen

-- Dipl.-Inf. Steffen Liebergeld <steffen@...37...> Security in Telecommunications TU Berlin/ Deutsche Telekom Laboratories Ernst-Reuter-Platz 7, 10587 Berlin Phone: +30 8353 58 263 Web: http://www.t-labs.tu-berlin.de/sect

-- Sven Fülster xms@...38...

Hello Steffen,

On Fri, May 21, 2010 at 12:36:50PM +0200, Steffen Liebergeld wrote:

This actually brought me on the right track. It turns out, that I was linking a library to init, which was not actually needed. I removed it, and the problem is gone.

Please post the name of the library you removed from your list. This gives us the chance to investigate options to remove this pitfall once and for all.

Happy hacking