➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2020-03-01 12:15 by toonn, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg363057 - (view) | Author: (toonn) | Date: 2020-03-01 12:15 | |
We got a report about a crash which seems to happen in the curses library when a user pressed ^4. How do we go about debugging this? https://github.com/ranger/ranger/issues/1859 |
|||
| msg363066 - (view) | Author: Serhiy Storchaka (serhiy.storchaka) *  |
Date: 2020-03-01 14:45 | |
It is not related to curses and Python. Run arbitrary program (for example `cat` or `sleep 100`) and press Ctrl-4. You will get a core dump. This is because your terminal generates the signal SIGQUIT on Ctrl-4, and default action on SIGQUIT is core dump. So it all works as expected. If you want to change it, ignore the signal. |
|||
| msg363089 - (view) | Author: (toonn) | Date: 2020-03-01 20:16 | |
Vim can handle ^4 just fine while still responding to SIGQUIT though. Is there a way to determine where the signal's coming from to decide whether to react to it? |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:27 | admin | set | github: 83992 |
| 2020-03-01 20:16:21 | toonn | set | messages: + msg363089 |
| 2020-03-01 14:45:29 | serhiy.storchaka | set | status: open -> closed nosy: + serhiy.storchaka messages: + msg363066 resolution: not a bug stage: resolved |
| 2020-03-01 12:15:46 | toonn | create | |