Get "segment fault" when launch python only in warp

Discord username (optional)

No response

Operating System

MacOS

Operating System and Version

macOS Sonoma 14.0

Local Shell Version

5.9

Remote Shell Version

4.2.46(2)-release

Warp Version

v0.2023.10.17.08.03.stable_02

I have tried commenting out my system & user rcfiles and warp still will not bootstrap

• Yes

Screenshots

When I run python on my server with warp, I got segment fault.(fig 1) The same python run successfully with other terminals.(eg fig.2 with vscode terminal, I also test original terminal app on Mac).
fig3 and fig4 show the output backtrace when I try "gdb python" in warp.
I'm not sure if this can be reproduced on others' system and I have run python successfully with warp on this system for about half a year.

Include shell xtrace output

ssh succeed and no output.

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa

None

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Start by reproducing the python segmentation fault over SSH in Warp on macOS Sonoma, then compare it with Terminal or VS Code and inspect the gdb python backtrace shown in the report. Done means the same remote Python command runs successfully in Warp without a segmentation fault.