On Mon, Feb 25, 2019 at 7:27 PM John Reiser <jreiser@xxxxxxxxxxxx> wrote:
On 2/25/19 4:26 PM, Richard Shaw wrote:
> apiextractor builds but pretty much all the tests fail. I got this from gdb in a mock chroot but not sure how to get more (debuginfo install in a chroot?)
>
> (gdb) run
> Starting program: /builddir/build/BUILD/apiextractor-0.10.10/x86_64-redhat-linux-gnu/tests/testvoidarg
> Missing separate debuginfos, use: dnf debuginfo-install glibc-2.29-7.fc30.x86_64
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> ********* Start testing of TestVoidArg *********
> Config: Using QTest library 4.8.7, Qt 4.8.7
> PASS : TestVoidArg::initTestCase()
>
>
> Program received signal SIGSEGV, Segmentation fault.
> TestVoidArg::testVoidParsedFunction (this=<optimized out>) at /builddir/build/BUILD/apiextractor-0.10.10/tests/testvoidarg.cpp:41
> 41 QCOMPARE(addedFunc->arguments().count(), 0);
> Missing separate debuginfos, use: dnf debuginfo-install glib2-2.59.2-1.fc30.x86_64 libgcc-9.0.1-0.4.fc30.x86_64 libstdc++-9.0.1-0.4.fc30.x86_64 libxml2-2.9.9-2.fc30.x86_64 libxslt-1.1.32-4.fc30.x86_64 openssl-libs-1.1.1a-2.fc30.x86_64 pcre-8.43-0.1.RC1.fc30.1.x86_64 qt-4.8.7-44.fc30.x86_64
> xz-libs-5.2.4-5.fc30.x86_64 zlib-1.2.11-15.fc30.x86_64
> (gdb) thread apply all bt full
That test 'testvoidarg' succeeds for me (normal termination, no SIGSEGV) on Fedora 28 and Fedora 29.
Yes, it only seems to affect f30/Rawhide with GCC 9 (though I'm not sure it's the culprit).
The traceback says:
> 41 QCOMPARE(addedFunc->arguments().count(), 0);
so the suggestion is to check if addedFunc->arguments() is NULL.
Thanks,
Richard
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
