Thu 19 May 2016 11:24:20 AM UTC, original submission:
When running from the GUI, the code
causes the GUI to hang, requiring ^C from the lauching terminal or "force quit" from the window manager. (Is "crash" the right item group for this?)
Running under gdb gives the following unhelpful stack trace:
This doesn't occur with FLTK or gnuplot.
If it is run with --no-gui, then the interpreter remains responsive, but the figure window seems to hang (it doesn't redraw on expose events) until debug mode is exited. After that, it returns to normal.
With "dbstop image 201", i.e., the line
running these commands and then typing "dbcont" doesn't cause the freeze. I thought it may have something to do with the redraw caused by going to the prompt, but putting an explicit "drawnow" before that line doesn't help. Perhaps it is a timing issue -- however it is more reproducible than I'd expect from a race condition.
|