bpo-36459: Fix a possible double PyMem_FREE() due to tokenizer.c's to… · python-emscripten/cpython@cda139d · GitHub

1. python-emscripten
2. cpython

Repository navigation

• Code
• Pull requests
• Actions
• Projects
• Security and quality
• Insights

Commit cda139d

Browse filesBrowse the repository at this point in the historyBrowse files

ZackerySpytz

authored and

serhiy-storchaka

committed

bpo-36459: Fix a possible double PyMem_FREE() due to tokenizer.c's tok_nextc() (12601)

Remove the PyMem_FREE() call added in cb90c89. The buffer will be freed when PyTokenizer_Free() is called on the tokenizer state.

1 parent 796cc6e commit cda139d
Copy full SHA for cda139d

2 files changed

+1-1Lines changed: 1 addition & 1 deletion

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• Misc/NEWS.d/next/Core and Builtins
  • 2019-03-27-22-35-16.bpo-36459.UAvkKp.rst
• Parser
  • tokenizer.c

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎Misc/NEWS.d/next/Core and Builtins/2019-03-27-22-35-16.bpo-36459.UAvkKp.rst‎

Copy file name to clipboard

+1Lines changed: 1 addition & 0 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -0,0 +1 @@
	1	+ Fix a possible double ``PyMem_FREE()`` due to tokenizer.c's ``tok_nextc()``.

Collapse file

‎Parser/tokenizer.c‎

Copy file name to clipboardExpand all lines: Parser/tokenizer.c

-1Lines changed: 0 additions & 1 deletion

Original file line number	Diff line number	Diff line change
@@ -963,7 +963,6 @@ tok_nextc(struct tok_state *tok)
963	963	newbuf = (char *)PyMem_REALLOC(newbuf,
964	964	newsize);
965	965	if (newbuf == NULL) {
966		- PyMem_FREE(tok->buf);
967	966	tok->done = E_NOMEM;
968	967	tok->cur = tok->inp;
969	968	return EOF;

0 commit comments

Comments

0 (0)