On 2015-04-11 21:05-0400 Hazen Babcock wrote:

> It worked fine without the Qt components. Is there an output file that I 
> should send?

Excellent news on the Lubuntu front.

To answer your question, please send a compressed tarball containing
_all_ environment variables (you can capture a complete list of those
from bash using printenv >& printenv.out); the script output that you
capture with

scripts/comprehensive_test.sh >& comprehensive_test.sh.out

; and all shared, nondynamic, and static output_dir contents.  Here are
the files collected in those directories by the script on my own platform:

software@raven> ls ../comprehensive_test_disposeable/*/output_tree/
../comprehensive_test_disposeable/nondynamic/output_tree/:
clean.out                   installed_clean.out                make.out         
        traditional_clean.out
clean_ctest_plot_files.out  installed_cmake.out                make_install.out 
        traditional_make_interactive.out
cmake.out                   installed_make_interactive.out     
make_interactive.out     traditional_make_noninteractive.out
ctest.out                   installed_make_noninteractive.out  
make_noninteractive.out

../comprehensive_test_disposeable/shared/output_tree/:
clean.out                   installed_clean.out                make.out         
        traditional_clean.out
clean_ctest_plot_files.out  installed_cmake.out                make_install.out 
        traditional_make_interactive.out
cmake.out                   installed_make_interactive.out     
make_interactive.out     traditional_make_noninteractive.out
ctest.out                   installed_make_noninteractive.out  
make_noninteractive.out

../comprehensive_test_disposeable/static/output_tree/:
clean.out                   installed_clean.out                make.out         
        traditional_clean.out
clean_ctest_plot_files.out  installed_cmake.out                make_install.out 
        traditional_make_interactive.out
cmake.out                   installed_make_interactive.out     
make_interactive.out     traditional_make_noninteractive.out
ctest.out                   installed_make_noninteractive.out  
make_noninteractive.out

The Qt information you gave before is quite helpful for the report
which I intend to put together concerning Qt segfaults. And so is the
uname info which identifies your hardware as x86_64. (a.k.a AMD64 to
give AMD their due for coming up with that hardware design before
Intel copied it).

However, it would be good if you could also identify the exact Lubuntu
version you are using.  According to
<http://en.wikipedia.org/wiki/Lubuntu> that version number likely
ranges somewhere from 10.04 to 15.04.  On my Debian system, I
can get the Debian version from
/etc/debian_version

which yields 7.8 ==> 8th minor variant of 7th (Debian Wheezy) release
of Debian.

Do you have an equivalent file on your system which identifies the
Lubuntu version?

>
> Why do you think these Qt components fail in the tests, but work fine if they 
> are run independently? What is the testing framework doing that is not being 
> done from the command line?

My guess is nothing explictly different is being done.  Instead, you
are dealing with a severe memory management issue which can sometimes
(by accident) be symptomless and sometimes can result in segfaults. So
segfaults typically imply severe memory management issues, but the
converse is not always true. The only completely reliable way I know
of to identify severe memory management issues is using valgrind to
run the examples.  If such a valgrind run (say on examples/c/x00c -dev
pngwidget -o test.png -fam) shows severe memory management issues,
then the Qt libraries on Lubuntu are the likely source of this issue.
However, if that valgrind run shows no severe memory management issue,
but you are getting segfaults on the x00 example with ctest (either
run by hand after running "make all" or via the script), then that
would be a strong indication that there is something wrong with either
our ctest setup or our script.

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
__________________________

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to