On 25 Jan 2013, at 04:56, Moses McKnight wrote: > I'm using the latest svn of fltk 1.3, and I have a simple window with an > Fl_Output. When I call the value(const char*) function with a string I > get a segmentation fault, and running it in the debugger shows it > happens in the Fl_Widget::clear_changed() function, called at the > beginning of the Fl_Input_::static_value(const char* str, int len) > function. > > Any idea why this might be happening? I am using a number of Fl_Output > in other windows in this same application without any problems.
Without seeing more of your code, it's hard to say: a common reason for this sort of thing is that something (perhaps the string?) has been declared stack-automatic in some function, and has fallen out of scope before it is used... Does that sound likely here? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
