> what happened is that, all of a sudden, my app segfaults > always in some FLTK redraw function. It worked yesterday > evening but this morning, without me changing anything in > the code (really!) it started to segfault in linux (code > still works fine in windows). i tried to recompile fltk > (maybe some lib it depends on was updated and since i use a > self-made fltk-1.1.9 lib i thought that might have caused > this (my distribution ships 1.1.7 but i want 1.1.9)). but > it didnt help.
Build a fltk lib with debugging enabled, then link to that, then launch your app from gdb and when it crashes, you can "bt" in the gdb console to see where, and why, it dies. Or, if you are running Eclipse, it can run the gdb session for you graphically, which is probably easier. Either way, once you have the app built with a debug lib (and NOT stripped at link time!) then you can see all the fltk symbols and so forth and find out why it faults. That said, it sounds like memory allocation or a mishandled pointer. It worked before, you say, but does not now, even though you did not change it - probably the OS has mapped things into RAM a bit differently this time, and now you are tripping up... SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
