@Raziel
Quote:
ok, sorry for the long post (i try to cut it down to the essentials)
You can have the full log if needed
(I marked the libs and stuff)
Unfortunately it doesn't help, getting the main interface of bevel.image works and the next function called would be the constructor of my owb memory allocator which prints "Using OWB memory allocator ..." in the very first line, but it's trying to execute something instead which doesn't exist (not part of any executable, library, shared object nor kickstart module).
The only obvious difference when starting OWB for the 2nd time is that the only library which wasn't in RAM yet the 1st time (pthreads.library, ramlib output) doesn't have to be loaded from disk any more, but since it's not used that early it can't be the problem either.