On 2013-12-19 22:50-0000 Andrew Ross wrote: > I've now also run the scripts/comprehensive_test.sh test on my Ubuntu > system. I encountered some problems in that on several occasions, > without warning, by kde session died. It was not reproducible, but in > each case it was while running the test_interactive tests, mostly in > the install tree. I've never seen this when running the test > individually in serial so I don't know whether it is a parallel build > problem or some hardware problem.
I have never seen anything like that from my KDE desktop despite running scripts/comprehensive_test.sh many times recently with a high degree of parallel interactive results. However, right in the middle of one of my _non_ interactive tests my X server (from my X-terminal where I am displaying results) died, and that killed everything. But that only happened once in the last week and never before or after. So since that is not repeatable, I am going to attribute it to a networking (since X-terminals work over the network), hardware, or X server glitch. But your situation with repeated KDE issues sounds quite different, and another possibility to consider there is that your version of KDE may not be as stable as mine. If I were in your situation, I would shift to some much simpler desktop (fvwm is the one I am familiar with, but you may have your own favorite) to see if the problems continue. > > Eventually I managed to get through almost all the tests though. The > only issue I encountered was a segfault with the C++ qt_example for the > nondyndriver case. Valgrind shows an invalid call to free / delete and > a memory access violation. The shared case is fine with valgrind so I > assume it is something about the static drivers. > > For the fully static case I do not get a segfault, but valgrind shows a > load or invalid reads in wx libraries ?!? > > Alan, do your tests reproduce this? I'll try a debug build to see if I > can get to the bottom of it. qt_example has had a severe memory management issue in the recent past (say over the last year or so) which I worked around by not permitting qt_example to be built for the static drivers case (e.g., for the PLplot-5.9.10 release). But my recent build-system changes for the Qt4-related parts of the PLplot build solved that issue (as confirmed by valgrind) so I enabled qt_example again for the static drivers case. But in light of your seeing more symptoms, I will check that again with valgrind runs for my system version of Qt4 and also the epa_build version of Qt4 and get back to you with those results. Please keep in touch on what your further investigation finds as well. It's possible the qt_example memory management trouble only occurs for certain versions of Qt4. 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); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); 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 __________________________ ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
