[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

Changes by Ned Deily : -- keywords: +patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

Changes by Ned Deily : -- keywords: +3.6regression -patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

STINNER Victor added the comment: Please update the issue title. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

INADA Naoki added the comment: (PYTHONMALLOC=malloc valgrind find it soon. :) -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

INADA Naoki added the comment: This is use after free, not overflow. This patch is based on Python 3.6, but I think 3.5 has same issue. I'll check it. -- keywords: +patch Added file: http://bugs.python.org/file46514/29438-sharedkey-useafterfree.patch

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

STINNER Victor added the comment: You may try to reproduce with a release build and PYTHONMALLOC=debug to check for buffer over/underflow. -- ___ Python tracker ___ _

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

INADA Naoki added the comment: 4385 int was_shared = cached == ((PyDictObject *)dict)->ma_keys; 4386 res = PyDict_SetItem(dict, key, value); 4387 if (was_shared && cached != ((PyDictObject *)dict)->ma_keys) { 4388

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

INADA Naoki added the comment: valgrind output is here. https://gist.github.com/methane/3c010daba71a374fd0b6a41a0d98e3ff It seems another bug relating to key-sharing dict... -- nosy: +inada.naoki ___ Python tracker

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

Xiang Zhang added the comment: I could reproduce this using Audric's command. And yes, debug build doesn't suffer from this crash. Nosy Victor. DEBUG:root:Called with: ['/tmp/minimal_crash.py', '-d', 'sqlite:///crash.db', '-v'] INFO:__main__:Connecting to DB 'sqlite:///crash.db' INFO:sqlalchem

[issue29438] SIGSEGV in PyObject_Malloc on python 3.6 and 3.7

New submission from Audric Schiltknecht: I've managed to create a minimal test file that causes python to crashe when run with python 3.6.0 (packaged in my distribution or from hg repository), 3.6 branch from hg repository and 3.7 branch from hg repository, but works fine on 3.5.3 and 3.5 bran