Paul Kienzle <pkienzle@...537...> writes:
[segfaults]
Is there something in the last couple of weeks which might cause this?
Some changes in font handling caused segfaults for me, and it turned out
to be a bug in an old version of freetype:
http://article.gmane.org/gmane.comp.python.matplotlib.general/10062
Try running python under gdb, or using strace/truss/ktrace to see what
is happening right before the segfault.
--
Jouni K. Sepp�nen
Jouni K. Sepp�nen wrote:
Paul Kienzle <pkienzle@...537...> writes:
[segfaults]
Is there something in the last couple of weeks which might cause this?
Some changes in font handling caused segfaults for me, and it turned out
to be a bug in an old version of freetype:http://article.gmane.org/gmane.comp.python.matplotlib.general/10062
Try running python under gdb, or using strace/truss/ktrace to see what
is happening right before the segfault.
I'm not able to reproduce anything amiss on my Linux box.
I would try Jouni's suggestion, and if that doesn't work, please try going back to revision 3762, which is before I made a number of changes to the memory management of font buffers. If that works, but HEAD doesn't a traceback from gdb would be useful.
Cheers,
Mike