Thanks for the report. Note that Android support is absolutely experimental and far from being finished (I'd say not even beta state). Anyway...

Are you sure the crash happens exactly in that line (1343) ? This would mean that the internal member path_ is null which should IMHO not happen when Node::find() is called (but I'm not sure about this at all). I can't test with android, and your backtrace appears to be incomplete, for instance there's no call to Fl::option(Fl::Fl_Option) in Fl_Button::handle(int) - it calls Fl::visible_focus() though which calls Fl::option(Fl::Fl_Option) indirectly. Unfortunately line numbers are missing as well.

Did you build FLTK with debugging info enabled? If not, can you please do it and try again? Note that you need to enable debugging with CMake implicitly, e.g. with the commandline switch -DCMAKE_BUILD_TYPE=Debug, this is not the default. I don't know how to do this with the Android build though.

Not sure how to best handle it. Should find() return null in that case?

Neither am I. The comment says: "... this method will always return a valid node ..." but there's a code path (which is not memory allocation related) that returns 0. This needs further investigation.

Another question: you wrote "segfault during callbacks" but also "Doesn't matter if a callback is set or not". When exactly does it crash? Right after the start (when Fl::visible_focus() is called for the first time) or when you click the button?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.