On 11/15/2016 02:46 AM, Alan W. Irwin wrote:
>>
>> All the file based Qt devices are failing for me in ctest. This is an
>> example error message:
>>
>> test 17
>>       Start 17: examples_pngqt
>>
>> 17: Test command: /bin/bash "-c"
>> "EXAMPLES_DIR=/home/hbabcock/Code/plplot-build/examples
>> SRC_EXAMPLES_DIR=/home/hbabcock/Code/plplot/examples
>> OUTPUT_DIR=/home/hbabcock/Code/plplot-build/ctest_examples_output_dir
>> VC_CTEST_DIRECTORY= ./plplot-test.sh --verbose --front-end=c
>> --device=pngqt"
>> 17: Test timeout computed to be: 1500
>> 17: Testing front-end c
>> 17: x00c
>> 17: x01c
>> 17: x02c
>> 17: ./test_c.sh: line 32: 16690 Segmentation fault      (core dumped)
>> $DEBUG_CMD "$cdir"/x${index}${lang} -dev $device -o
>> "${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> test.error >|
>> "${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt
>> 17/24 Test #17: examples_pngqt ...................***Failed    0.61 sec
>>
>
> Is this segfault occurring for Qt5 or Qt4?  If the former, my advice is
> to try Qt4 instead.

This is happening with Qt4, specifically:

$ /usr/bin/qmake-qt4 --version
QMake version 2.01a
Using Qt version 4.8.7 in /usr/lib/x86_64-linux-gnu

> My current testing hasn't detected this segfault, but that doesn't
> mean much since that is the nature of memory management issues; they
> sometimes segfault and they sometimes do not.  By the way, the "x02c"
> prompt
> occurs at the start of that portion of the test (see
> plplot_test/test_c.sh.in) so that is
> the example that segfaulted, not x03c.  So you might or might
> not see a segfault with
>
> ./x02c -dev pngqt -o ex2.png
>
> However, a valgrind run on that here (for the Qt5 case) does show
> memory management issues (invalid reads) that do not lead to segfaults
> for me but which lead to segfaults (like you have seen) for others.
> Furthermore, similar valgrind runs on x00c, x01c and x03c shows no
> such memory management issues.  I will take a look at that memory
> management incompatiblity between the qt devices and example 2 _if_
> that issue also shows up for Qt4, but if this is a Qt5-only issue I
> won't bother with it because I attribute (see below) Qt5-only memory
> management issues to the immaturity of Qt5 compared to Qt4.

Thank you for the correction, that command does not segfault:
./x02c -dev pngqt -o ex2.png

But it does segfault in family mode:
./x02c -fam -dev pngqt -o ex2.png

-Hazen

------------------------------------------------------------------------------
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to