From: Andrew R. <and...@us...> - 2010-05-25 09:54:50
|
On Tue, May 25, 2010 at 08:34:17AM +0100, Leo wrote: > On 2010-05-25 06:18 +0100, Alan W. Irwin wrote: > > There is an outstanding Mac OS X issue with qt devices that Hazen just > > discovered which might indicate those devices are not thread safe (at least > > on that platform). > > > > Are all your troubles for qt devices or have you tried other devices > > which also show errors? > > The lisp is running on linux. I have no qtwidget on osx yet. I have > moved lisp to the remote server because it has more cpus and memory. In > my tests in previous posts I usually did them with both xcairo and > qtwidget to be absolutely sure. > > > For example, it would be worthwhile to check the svg device (a modern PLplot > > device that does not depend on external libraries at all), and cairo devices > > assuming you have the pango/cairo library stack (a subset of the GTK+ stack > > of libraries) installed. > > No crash with svg. > > > Once we get a comprehensive feel for which devices have issues for you and > > which do not, it might give us a better idea for what to look for > > (or whether your issue is related to Hazen's). > > Thanks in advance. So just to be clear, you have only observed the crash with the following interactive devices: xcairo, qtwidget Have you tried xwin on Linux? This has far fewer external dependencies and the thread support for screen refresh is in the driver (so we have more chance of debugging!) You have not observed problems with psc or svg drivers. What about the qt or cairo file based drivers (e.g. pscairo / epsqt)? You might try running with valgrind as an alternative to gdb. It tends to be quite good at finding issues related to memory access / memory allocation. Andrew |