[issue35261] readline.c: PyOS_InputHook not protected against SIGWINCH

STINNER Victor added the comment: You don't use properly ctypes. This issue is unrelated to signals. The fix is: HOOKFUNC = CFUNCTYPE(c_char_p,). -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue35261] readline.c: PyOS_InputHook not protected against SIGWINCH

pmpp added the comment: expected result would look like: python3.6 -i -u -B pih.py >>> Segmentation fault (core dumped) -- ___ Python tracker ___

[issue35261] readline.c: PyOS_InputHook not protected against SIGWINCH

pmpp added the comment: oops use: python3 -i -u -B pih.py to run crash test -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue35261] readline.c: PyOS_InputHook not protected against SIGWINCH

STINNER Victor added the comment: Can you please describe what happens and what is the expected behavior? When I run "python3 pih.py", the script exits immediately and then a get many "kill: (5441) - No such process" errors in bash. -- nosy: +vstinner ___

[issue35261] readline.c: PyOS_InputHook not protected against SIGWINCH

New submission from pmpp : when using PyOS_InputHook from within readline module two signals are to be handled SIGINT and SIGWINCH SIGINT is really usefull in case hook has a problem though in some case it should be nice to prevent it too (async loop in repl background) but SIGWINCH is an ann