On 28 Feb 2009, at 15:01, jaws wrote: > At the moment my application run properly with fltk 1.3.x built > with i386-linux-gcc. If I try to run the same application built for > avr32 it works if I use the fltk1.1.9. If I use the fltk 1.3.x it > exits with a SIGABORT signal and right now I didn't understand how > to debug and find the cause because the gdb stack is corrupted. > Any idea to solve or investigate this problem? How is it possible > that the change of the library produce this strange effect?
Hard to say, on the basis if the information you have provided. My first, best (and quite possibly only!) guess is that you have inadvertently linked some of the 1.1.9 headers or include files in your 1.3 build. Note that the 1.1.x series and 1.3.x series have include files with the same names and very (very!) similar API but very different underlying ABI, so it is quite possible to compile or link your application in a sort of "hybrid" state, partly 1.1.9, partly 1.3.x, and have the link complete successfully. I know I have done this, as have others. The problems do not come to light until you run your code, and the executable trips up because of the incompatibilities in the ABI. So, clean out your build, check what paths the compiler is using to pull in the header files, check out what paths the linker is using to pull in the libraries. Make sure everything is correct. Then see how you get on. If it still fails... You'll have to provide more info on the failure. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
