> Does anyone have a clue? Mysterious indeed. No idea what it is, but to debug it maybe:
- if it is to do with the way you use fltk, can you compile/run the same code on a desktop machine (maybe with valgrind or similar, if it is a memory issue) and see if it manifests the same error? If the fault is reproducible elsewhere, it might be easier to pin down. - can you run gdb on your target and get it to break on the first error. A backtrace at that point *might* show where things were when it went awry? - memory leaks? - something else... SELEX Galileo Ltd 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
