[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-28 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-28 Thread miss-islington
miss-islington added the comment: New changeset 6fd3c852b15820480ad2ea83e7857615c4976304 by Miss Islington (bot) in branch '3.7': bpo-36459: Fix a possible double PyMem_FREE() due to tokenizer.c's tok_nextc() (12601)

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-28 Thread miss-islington
miss-islington added the comment: New changeset dffe90ee0eaf77785ad3d4ad7fb3249430ed1cb9 by Miss Islington (bot) in branch '2.7': bpo-36459: Fix a possible double PyMem_FREE() due to tokenizer.c's tok_nextc() (12601)

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-28 Thread miss-islington
Change by miss-islington : -- pull_requests: +12545 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-28 Thread miss-islington
Change by miss-islington : -- pull_requests: +12544 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-28 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: New changeset cda139d1ded6708665b53e4ed32ccc1d2627e1da by Serhiy Storchaka (Zackery Spytz) in branch 'master': bpo-36459: Fix a possible double PyMem_FREE() due to tokenizer.c's tok_nextc() (12601)

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-27 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-27 Thread Zackery Spytz
Change by Zackery Spytz : -- keywords: +patch pull_requests: +12541 stage: -> patch review ___ Python tracker ___ ___

[issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()

2019-03-27 Thread Zackery Spytz
New submission from Zackery Spytz : Commit cb90c89de14aab636739b3e810cf949e47b54a0c added a PyMem_FREE(tok->buf) call in tok_nextc() if a PyMem_REALLOC() call fails. This will cause a double free when PyTokenizer_Free() is called on the tokenizer state. -- components: Interpreter