Segfault on Windows git bash (msys) when using bash tool with cwd #11043

Activity

1. pschiel

   added

   bugSomething isn't workingSomething isn't working

   on Jan 28, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 28, 2026
3. github-actions

   added

   windows

   on Jan 28, 2026
4. github-actions commented on Jan 28, 2026

   

   github-actionsBot

   on Jan 28, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Windows: Git Bash auto-detection derives invalid bash.exe path #10871: Windows: Git Bash auto-detection derives invalid bash.exe path (related issue with Git Bash path handling on Windows)
   • Ctrl-C doesn't clear the input on Windows, it crashes #10538: Ctrl-C doesn't clear the input on Windows, it crashes (another Windows bash/PTY issue)

   The root cause appears to be related to Windows path handling (backslashes) in the bash tool's cwd parameter. Issue #10871 specifically addresses path handling issues with Git Bash on Windows that could be related.

   Feel free to ignore if none of these address your specific case.
5. pschiel commented on Jan 31, 2026

   

   pschiel

   on Jan 31, 2026

   ContributorAuthor

   More actions

   details:

   • segfault occurs in spawn() via Node's child_process module
   • libuv layer: when spawn() tries to change to a non-existent directory, the underlying uv_spawn call dereferences a null pointer
   • Bun doesn't validate cwd exists before attempting the spawn operation
   • Segfault at 0x0: The null pointer dereference causes immediate segfault at address 0x0

   added isDir checks in bash tool, pty and lsp (where user/agent input could happen) to avoid this
6. pschiel

   closed this as completedon Feb 22, 2026