> > Another useful test would be to add
> >
> > fl_alert("after Fl::run()";
> >
> > at the end of the program (as it says, after the Fl::run()
> > statement) to see if Fl::run() is terminated and the program
> > hangs somewhere in the destructors or other Windows runtime
> > code.
> >
> > This code at the end of test/device.cxx works as expected
> > here on Windows 7:
> >
> > --- end of test/device.cxx ---
> >
> > Fl::run();
> > fl_alert("after Fl::run()");
> > return 0;
> > };
> >
> >
> > Albrecht
>
> With this code at end, yes I receive the message and the process remain
> zombie, so you are right could be something with destructors.Domingo: we are progressing. Could you run the test with the final fl_alert() call under gdb and see what happens after the Fl::run(); statement? It may even be simpler to just finish the program with Fl::run(); int dummy=0; dummy++; return 0; } put a breakpoint at the dummy++; statement and follow what gdb sees after this statement. Sorry, I can't reproduce the zombie, so can't do any of that myself. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
