> One common cause for errors "within" FLTK is sending a method > a pointer > to automatic data. The "label(const char* text)" function > bit me badly > until I realized that it didn't actually copy the string that > I sent it.
Although, naturally, copy_label() does copy the label, which is why both methods exist, of course. I'm not sure that the OP's problem can be automatic data though, not if, as was indicated, it is related to the loading of this large data buffer. That presumably would not get written onto the stack, would it? Surely that would go into memory allocated on the heap? Of course, loading this large data buffer probably does change the alignment in RAM of various other objects, so I there is a leak somewhere else, that might expose it. 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
