[issue43664] Long computations in pdb.run() lead to segfault

Serhiy Storchaka added the comment: It is an old known issue, it is not specific to pdb, but happens with compile(), and it is not fixed yet. >>> compile("+0"*100, '?', 'eval') Segmentation fault (core dumped) Stack overflow in recursive call of validate_expr() in at Python/ast.c:223.

[issue43664] Long computations in pdb.run() lead to segfault

Xinmeng Xia added the comment: pdb.run() seems crashing different positions of Python (Python/ast_opt.c:488 for pdb.run, Python/ast_opt.c:494 for compile()). But the commit 364d0d20f924071b749e5a889eca22628f4892a3, PR 23744, bpo-42609 for compile() also fix this bug in pdb.run(). Should we

[issue43664] Long computations in pdb.run() lead to segfault

Karthikeyan Singaravelan added the comment: This looks like a duplicate of https://bugs.python.org/issue42714 which has been fixed. -- nosy: +xtreak ___ Python tracker ___

[issue43664] Long computations in pdb.run() lead to segfault

Ronald Oussoren added the comment: ```pdb.run(...)``` is ends up in ```bdb.Bdb.run```, which uses compile and exec to run the code. And indeed: >>> compile("1+2" * 100, "-", "exec") zsh: segmentation fault python3.9 -- components: +Interpreter Core nosy: +ronaldoussoren

[issue43664] Long computations in pdb.run() lead to segfault

New submission from Xinmeng Xia : Long computations in pdb.run() lead to interpreter crashes. Crash example === Python 3.9.2 (default, Mar 12 2021, 15:08:35) [GCC 7.5.0] on linux Type "help", "copyright", "credits" or "license" for more