Launching the BusyBox shell from Windows' CMD or PowerShell and pressing Ctrl+C will overlap both shells
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- bash, c, powershell
- 领域
- cli, operating-systems
调研方向
Start by reproducing the issue with bash.exe or sh.exe launched from Windows CMD or PowerShell, including after Ctrl+C interrupts a command such as sleep 10. Trace the terminal and interrupt handling involved in those shell entry points; done means Ctrl+C no longer leaves both shells receiving input or printing prompts.
由索引模型根据 Issue 内容生成。
描述
I noticed this when trying to setup for myself an easy-to-use shell environment.
If I open a CMD or PowerShell window, and then launch bash.exe from the command line, and then I press Ctrl+C, it will appear like both CMD/PowerShell and the BusyBox shell will fight for my terminal. Both will print their prefixes at the same time, and it seems that each of my keystrokes is sent in alternance to each shell, so if I were to type "exit" and enter, one shell would get "xt" and the other "ei" and enter. The terminal becomes essentially unusable.
The Ctrl+C bug passes through any running command, so if I'm within the BusyBox shell running another program like GCC or even sleep 10, just one Ctrl+C will both interrupt the running program as expected, and cause the bug I describe. Pressing Ctrl+C more times does not appear to change anything, the only way that I'm aware of to work around the problem is to close and reopen the terminal.
Straightforward reproduction steps:
- Launch CMD or Powershell
- From the shell, execute BusyBox's
bash.exeorsh.exe - Optionally, launch a program that takes time, like
sleep 10 - Press Ctrl+C once
The effects should be immediately visible; pressing return a few times shows the clash between the shells.
I'm not entirely sure where is the most relevant place to report this issue since I'm not sure what's in cause here; I can bump the bug report to BusyBox or elsewhere if needed.
- 主要语言
- C
- 星标
- 5k
- 派生
- 408
- 平均合并
- 4 小时 40 分钟
- 30 天内合并 PR
- 2
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
skeeto/w64devkit 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 4/5 3-5 天 新手友好度 46/100
-
难度 3/5 1-2 天 新手友好度 52/100
-
难度 5/5 一周以上 新手友好度 25/100
-
难度 5/5 一周以上 新手友好度 35/100
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
sk3llo/ffmpeg_kit_flutter#176 ·
-
Synth suite fails unless run from the repo root: signal_flow's default machine path is cwd-relative未关闭bug
难度 2/5 1-3 小时 新手友好度 80/100
Nimblesite/osprey#370 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 78/100