It is now official, the cause of the mysterious gcc 3.3.5 exception

handling failure is definately sjlj. Only enable it for the apparently
broken gcc 3.3.3 toolchain, which _does_ need it for exception handling
to work properly.