[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Serhiy Storchaka added the comment: Opened issue39831. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ P

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Serhiy Storchaka added the comment: Actually there is a leak in PyErr_WarnEx(). -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Change by STINNER Victor : -- resolution: fixed -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Change by Serhiy Storchaka : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Charalampos Stratakis added the comment: After this change, the arm64 buildbots are reporting reference leaks: 1:03:24 load avg: 0.95 Re-running failed tests in verbose mode 1:03:24 load avg: 0.95 Re-running test_capi in verbose mode test_capi leaked [4, 4, 4] references, sum=12 e.g. https://

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> crash versions: +Python 3.9 ___ Python tracker ___ __

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Serhiy Storchaka added the comment: New changeset a7b8a969eb3daacb1fcb029a8c5fecb5d09c964b by Serhiy Storchaka in branch '3.8': [3.8] bpo-38913: Fix segfault in Py_BuildValue("(sGH-O)", ...) if entered with exception raised. (GH-18656). (GH-18732) https://github.com/python/cpython/commit/a7b

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Change by Serhiy Storchaka : -- pull_requests: +18089 pull_request: https://github.com/python/cpython/pull/18732 ___ Python tracker ___

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Serhiy Storchaka added the comment: New changeset 28d0bcac8b7e6dbd28311f1283dabb6a4d649fcb by Serhiy Storchaka in branch 'master': bpo-38913: Fix segfault in Py_BuildValue("(s#O)", ...) if entered with exception raised. (GH-18656) https://github.com/python/cpython/commit/28d0bcac8b7e6dbd2831

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +18017 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18656 ___ Python tracker ___

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Change by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Łukasz Langa added the comment: Sadly, this missed the train for 3.8.2 as well. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Łukasz Langa added the comment: Note: this is going to miss Python 3.8.1 as I'm releasing 3.8.1rc1 right now. Please address this before 3.8.2 (due in February). -- ___ Python tracker __

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

danielen added the comment: The problem arises from this code in do_mktuple(), staring at line 394 in modsupport.c: if (**p_format == '#') { ++*p_format; if (flags & FLAG_SIZE_T) n = va_arg(*p_va, Py_ssize_t); els

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

danielen added the comment: It is not reproducible with PY_SSIZE_T_CLEAN defined. -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Steve Dower added the comment: Does it depend on whether PY_SSIZE_T_CLEAN is defined? -- nosy: +steve.dower ___ Python tracker ___

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Matthias Klose added the comment: seen with the current 3.8 branch. -- keywords: +3.8regression nosy: +doko, lukasz.langa priority: normal -> release blocker ___ Python tracker __

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

New submission from danielen : The following code results in a segmentation fault in CPython 3.8 while executes fines (raises a SystemError) in CPython 3.7. PyObject* debug(PyObject *self, PyObject *args) { const char * debug = "debug"; PyErr_SetString(PyExc_ValueError, "debug!