Sofian Brabez added the comment:
Thanks Victor, it's clear now.
About the updates of the crashers, I sent the updated patches to update them in
PR [3] before the following issue [1] and PR [2] but the other seems to have
been merged already.
It seems my submission was totally forgo
Sofian Brabez added the comment:
It's been a while and I still have no clear guidance from there of what
developers want to do.
Follow-up on this again to see if requires updates or just close it.
--
___
Python tracker
<https://bugs.py
Sofian Brabez added the comment:
Any ETA? I would appreciate to see my contribution being merged.
Batuhan, the current code is not doing what it's supposed to do in
bogus_code_obj.py (i.e. no crash after 3.8 and above in master and branches).
This still make the issue valid I
Change by Sofian Brabez :
--
pull_requests: +22340
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23448
___
Python tracker
<https://bugs.python.org/issu
Sofian Brabez added the comment:
Thanks Dennis for pointing me the crashers, I was not aware of them.
I have added a new crash test to cover multiple crashes in different
interpreter versions. Current bogus does not crash where it could be possible
to crash in older and newer interpreter
Sofian Brabez added the comment:
Linux, FreeBSD and MacOSX crash reports and backtraces joined in the zip.
Contributor Agreement 2020-09-23 signed.
--
Added file: https://bugs.python.org/file49611/crash-report-txt.zip
___
Python tracker
<ht
New submission from Sofian Brabez :
This PoC is causing a local crash of python interpreters version
2.7,3.6,3.7,3.8 and 3.9.
By creating a code object of size 0 with a POP_TOP opcode, in Python/ceval.c
the call to Py_DECREF(value) on a NULL pointer lead to a segmentation fault of
the
