On 2009-03-12 20:21-0000 Andrew Ross wrote:

>
> With current svn all the qt file devices produce a segfault when
> run with more than one page of output, e.g. example 2. This happens
> with ctest, or if calling the examples direct, e.g.
> ./x02c -fam -dev bmpqt -o test.bmp
> [...]This happens after the second page has been generated, so I assume it
> is related to closeQtApp being called multiple times (probably as
> plP_tidy is called at the end of each page). Alan / Alban, can you confirm
> this?

There were memory management issues, but I believe those were fixed for
Alban's recent reorganization/update (revision 9729).

Do you still get the same issues for the latest version (revision 9731)?  I
can detect no segfaults for those.  Specifically, here is the relatively
benign valgrind results for the same example you mentioned above.

softw...@raven> valgrind c/x02c -dev bmpqt -o test%n.bmpqt -fam -fflen 2
==18564== Memcheck, a memory error detector.
==18564== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==18564== Using LibVEX rev 1854, a library for dynamic binary translation.
==18564== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==18564== Using valgrind-3.3.1-Debian, a dynamic binary instrumentation
framework.
==18564== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==18564== For more details, rerun with: -v
==18564== 
==18564== 
==18564== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 301 from 3)
==18564== malloc/free: in use at exit: 196,832 bytes in 3,442 blocks.
==18564== malloc/free: 50,889 allocs, 47,447 frees, 30,680,826 bytes
allocated.
==18564== For counts of detected errors, rerun with: -v
==18564== searching for pointers to 3,442 not-freed blocks.
==18564== checked 1,112,096 bytes.
==18564== 
==18564== LEAK SUMMARY:
==18564==    definitely lost: 1,784 bytes in 34 blocks.
==18564==      possibly lost: 0 bytes in 0 blocks.
==18564==    still reachable: 195,048 bytes in 3,408 blocks.
==18564==         suppressed: 0 bytes in 0 blocks.
==18564== Rerun with --leak-check=full to see details of leaked memory.

I get similar results for example 8 as well.

As usual, the above is for Debian Lenny on 64-bit hardware.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to