On Sat, Mar 13, 2010 at 5:50 PM, Alan W. Irwin <ir...@beluga.phys.uvic.ca> wrote: > Hi Hez: > > Here is how to quickly generate the segfault that is mentioned in the > subject line from an initially empty build tree. > ... > > So it appears line 1488 of cairo.c is making a call to cairo with something > essential undefined with -dev pngcairo. -dev xcairo did not have > any such valgrind errors. Also, revision 10861 of cairo.c generated no > valgrind errors (or segfaults) with -dev pngcairo and produced a good > looking png result. > > Hope these multiple clues help you to get quickly to the bottom of this > segfault. >
Alan, Thank you for the detailed report. It was indeed a xcairo-specific logic error, where the Xlib-based Cairo surface was always referenced if the xcairo device was enabled at compile time, rather than only being used when the xcairo driver is actually in use. I'm very sorry I let such an error slip by! Testing looks ok here with revision 10865. Please let me know if it works for you now as well. Hez ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
