Bug#909379: segfault when leaving the python3-dbg interpreter

2019-03-10 Thread Stefano Rivera
Hi Picca (2019.03.09_20:56:03_-0800) > I'm interested to hear about any API/ABI breakage in cffi modules, but I > just can't find the culprits, here. Sorry, was tired and closed the wrong clone of the bug. However, this bug is also no longer reproduceable, as mentioned in message 62 from Thomasz.

Bug#909379: Info received (Bug#909379: segfault when leaving the python3-dbg interpreter)

2018-09-23 Thread Andreas Beckmann
On 2018-09-23 19:22, Tomasz Rybak wrote: > IFAIR PyOpenCL was never built against Python3.7. > Feel free to do NMU, but be careful with current git version (-3). As a binNMU by the release team should be sufficient, there should be no need for anyone to NMU. Andreas PS: feel free to ping me if

Bug#909379: [Pkg-opencl-devel] Bug#909379: Bug#909379: Info received (Bug#909379: segfault when leaving the python3-dbg interpreter)

2018-09-23 Thread Tomasz Rybak
IFAIR PyOpenCL was never built against Python3.7. dpkg -L python3-pyopecl and dpkg -L python3-pyopencl-dbg show only files related to Python3.6. I started working on update of package (and pushed changes to git repository) but haven't yet uploaded new version. compat 11 scripts mess a bit with -doc

Bug#909379: segfault when leaving the python3-dbg interpreter

2018-09-23 Thread PICCA Frederic-Emmanuel
Hello Andreas, what about this build dependency ? python3-all-dbg Cheers

Bug#909379: segfault when leaving the python3-dbg interpreter

2018-09-23 Thread Andreas Beckmann
On 2018-09-23 14:54, Rebecca N. Palmer wrote: > This also happens on amd64 (backtrace follows), where it only affects > python3.7-dbg (not python3-dbg (3.6) or python3.7).  It happens on > interpreter exit, not on import. Given that the package python3-pyopencl-dbg Depends: python3-pyopencl (= 2

Bug#909379: [Pkg-opencl-devel] Bug#909379: Info received (Bug#909379: segfault when leaving the python3-dbg interpreter)

2018-09-23 Thread Rebecca N. Palmer
This also happens on amd64 (backtrace follows), where it only affects python3.7-dbg (not python3-dbg (3.6) or python3.7). It happens on interpreter exit, not on import. I suspect this is _not_ the new cffi version as such, because: - It does not affect pyzmq or pillow (which also use cffi and

Bug#909379: Info received (Bug#909379: segfault when leaving the python3-dbg interpreter)

2018-09-23 Thread PICCA Frederic-Emmanuel
Here a backtrace, So the segfault comes from the cffi backend. Since cffi is used during the pyopencl build,maybe something changed between the cffit versionduring the build and the current one. pyopencl was build with python-cffi all 1.11.5-1 and used with the cffi-backend 1.11.5-3. somaybe th

Bug#909379: segfault when leaving the python3-dbg interpreter

2018-09-22 Thread PICCA Frederic-Emmanuel
Hello, I rebuilt pyopencl, and it solved the problem... I do not know what is the real issue !!!

Bug#909379: segfault when leaving the python3-dbg interpreter

2018-09-22 Thread Picca Frédéric-Emmanuel
Package: python3-pyopencl-dbg Version: 2018.1.1-2 Severity: important hello, I was struggling on an autopkgtest failure forone of my packages (pymca) At the end I findout that the problem comes from pyopencl. When I try to import pyopencl, I get this. $ python3.7-dbg -c "import pyopencl" /usr/li