Author petr.viktorin
Recipients petr.viktorin
Date 2019-06-03.09:21:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559553697.78.0.201685591504.issue37140@roundup.psfhosted.org>
In-reply-to
Content
Hello,
I haven't investigated this fully yet, and won't be able to find time today. I'm forwarding the report here in case someone familiar with the code wants to take a look.

On Fedora, "clang" fails to build with Python 3.8, probably due this change (which was supposed to be Windows-only):
https://github.com/python/cpython/commit/32119e10b792ad7ee4e5f951a2d89ddbaf111cc5#diff-998bfefaefe2ab83d5f523e18f158fa4R413

According to serge_sans_paille: if ``self->b_ptr`` contains pointer, the ``memcpy`` creates sharing, and this is dangerous: if a ``__del__`` happens to free the original pointer, we end up with a dangling reference in ``new_ptr``. As far as I can tell, this is what happens in the clang bindings code.

Fedora discussion with link to logs: https://bugzilla.redhat.com/show_bug.cgi?id=1715016
History
Date User Action Args
2019-06-03 09:21:37petr.viktorinsetrecipients: + petr.viktorin
2019-06-03 09:21:37petr.viktorinsetmessageid: <1559553697.78.0.201685591504.issue37140@roundup.psfhosted.org>
2019-06-03 09:21:37petr.viktorinlinkissue37140 messages
2019-06-03 09:21:37petr.viktorincreate