DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2694 Version: 2.0-current Yes, you are right. The crash happened inside ~Node(), which should not related to vendor & application string. The crash happened in my very simple test case for my own application library. The test case is simple and nothing related to fltk2. The application library has two parts: C++ code on GUI using fltk2 and c code for all non-GUI cases. The mixture of c and c++ may cause the complexity, since c code and c++ code can invoke each other in either direction. I am testing a simple c function but unfortunately there is an c++ callback in the same c file (but no c++ invocation in the tested c function), that is the reason that fltk2 is linked to my testcase. In theory, with smarter linker, fltk2 should never be linked to my test case. My test case crashed with above call stack. But my application with proper fltk2 event loop works well. BTW, I did not use filechooser in my application or application library. Link: http://www.fltk.org/str.php?L2694 Version: 2.0-current _______________________________________________ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
