Hi Dmitry. I checked the code in sip5 and sip6 and found the same lines as in sip4, which raise the segmentation fault in sip4. So, there is a high probability all sip versions have the same bug. This is "using after free" bug, so it's hard to reproduce. Normally the probability of segmentation fault is very low. I reported the bug to p...@riverbankcomputing.com same time as to bugs.debian.org, but nothing happens :( Maybe my mail was filtered ? So I have no idea what to do next. What do you think?
-- Artem Rusanov вс, 9 янв. 2022 г. в 20:34, Dmitry Shachnev <mity...@debian.org>: > > Hi Artem, and sorry for delayed reply. > > On Tue, Nov 09, 2021 at 07:57:17PM +0300, Artem Rusanov wrote: > > Dear Maintainer, > > > > Sometimes during startup (depend on python code, comment line can affect > > this) my software crashes with segmentation fault in python-sip. > > sip4 is no longer developed. > > Please try with sip6 (which is available in Debian testing/unstable) or sip5 > (which is available in bullseye/stable). > > If the issue still happens with one of these versions, I suggest you to > report a bug to upstream mailing list (better with a minimal example): > > https://www.riverbankcomputing.com/mailman/listinfo/pyqt > > -- > Dmitry Shachnev
