[Python-modules-team] Bug#903263: sip-dev: segfaults building libarcus in Sid

Petter Reinholdtsen pere at hungry.com
Sun Jul 8 12:26:05 BST 2018


Package: sip-dev
Version: 4.19.11+dfsg-1
Severity: serious

Setting severity to serious, as this problem break the build of another
package.

When trying to build a new version of libarcus in Sid from the new git
repository on Salsa, the build fail because sip segfaults.

You should be able to reproduce the problem by running this:

  gbp clone https://salsa.debian.org/3dprinting-team/libarcus.git
  cd libarchus
  gbp buildpackage

Here is some information about the crash.  Not quite sure how to get a
more useful backtrace.

% (cd obj-x86_64-linux-gnu/; make)
/usr/bin/cmake -H/home/pere/src/debian/3d-printing/libarcus -B/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/CMakeFiles /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
make -f CMakeFiles/Arcus.dir/build.make CMakeFiles/Arcus.dir/depend
make[2]: Entering directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
cd /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/pere/src/debian/3d-printing/libarcus /home/pere/src/debian/3d-printing/libarcus /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/CMakeFiles/Arcus.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
make -f CMakeFiles/Arcus.dir/build.make CMakeFiles/Arcus.dir/build
make[2]: Entering directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
make[2]: Nothing to be done for 'CMakeFiles/Arcus.dir/build'.
make[2]: Leaving directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
[ 27%] Built target Arcus
make -f CMakeFiles/python_module_Arcus.dir/build.make CMakeFiles/python_module_Arcus.dir/depend
make[2]: Entering directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
[ 31%] Generating python/sipArcuspart0.cpp, python/sipArcuspart1.cpp, python/sipArcuspart2.cpp, python/sipArcuspart3.cpp, python/sipArcuspart4.cpp, python/sipArcuspart5.cpp, python/sipArcuspart6.cpp, python/sipArcuspart7.cpp
/usr/bin/cmake -E echo

/usr/bin/cmake -E touch /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart0.cpp /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart1.cpp /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart2.cpp /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart3.cpp /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart4.cpp /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart5.cpp /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart6.cpp /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python/sipArcuspart7.cpp
/usr/bin/sip -g -j 8 -c /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python /home/pere/src/debian/3d-printing/libarcus/python/Socket.sip
make[2]: *** [CMakeFiles/python_module_Arcus.dir/build.make:71: python/sipArcuspart0.cpp] Segmentation fault
make[2]: *** Deleting file 'python/sipArcuspart0.cpp'
make[2]: Leaving directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
make[1]: *** [CMakeFiles/Makefile2:70: CMakeFiles/python_module_Arcus.dir/all] Error 2
make[1]: Leaving directory '/home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu'
make: *** [Makefile:155: all] Error 2
% (cd obj-x86_64-linux-gnu; valgrind /usr/bin/sip -g -j 8 -c /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python /home/pere/src/debian/3d-printing/libarcus/python/Socket.sip)  
==19724== Memcheck, a memory error detector
==19724== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==19724== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==19724== Command: /usr/bin/sip -g -j 8 -c /home/pere/src/debian/3d-printing/libarcus/obj-x86_64-linux-gnu/python /home/pere/src/debian/3d-printing/libarcus/python/Socket.sip
==19724== 
==19724== Invalid read of size 1
==19724==    at 0x1131B6: ??? (in /usr/bin/sip)
==19724==    by 0x1FFF0004DF: ???
==19724==    by 0x1FFF0003EF: ???
==19724==    by 0x1FFF0004F7: ???
==19724==    by 0x3000000017: ???
==19724==    by 0x1FFF0004FF: ???
==19724==    by 0x1FFF00040F: ???
==19724==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==19724== 
==19724== 
==19724== Process terminating with default action of signal 11 (SIGSEGV)
==19724==  Access not within mapped region at address 0x0
==19724==    at 0x1131B6: ??? (in /usr/bin/sip)
==19724==    by 0x1FFF0004DF: ???
==19724==    by 0x1FFF0003EF: ???
==19724==    by 0x1FFF0004F7: ???
==19724==    by 0x3000000017: ???
==19724==    by 0x1FFF0004FF: ???
==19724==    by 0x1FFF00040F: ???
==19724==  If you believe this happened as a result of a stack
==19724==  overflow in your program's main thread (unlikely but
==19724==  possible), you can try to increase the size of the
==19724==  main thread stack using the --main-stacksize= flag.
==19724==  The main thread stack size used in this run was 8388608.
==19724== 
==19724== HEAP SUMMARY:
==19724==     in use at exit: 141,878 bytes in 576 blocks
==19724==   total heap usage: 988 allocs, 412 frees, 347,107 bytes allocated
==19724== 
==19724== LEAK SUMMARY:
==19724==    definitely lost: 821 bytes in 61 blocks
==19724==    indirectly lost: 650 bytes in 67 blocks
==19724==      possibly lost: 0 bytes in 0 blocks
==19724==    still reachable: 140,407 bytes in 448 blocks
==19724==         suppressed: 0 bytes in 0 blocks
==19724== Rerun with --leak-check=full to see details of leaked memory
==19724== 
==19724== For counts of detected and suppressed errors, rerun with: -v
==19724== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
% 

-- 
Happy hacking
Petter Reinholdtsen



More information about the Python-modules-team mailing list