Error in vscode IDE : Inappropriate ioctl for devicee
See original GitHub issuegdb-dashboard works with standart terminals, but when I run it in vscode IDE, DebugConsole gives me there errors:
(Not: I tried on XOrg, I am using Debian10)
e[31mCannot write the dashboard
Traceback (most recent call last):
File "<string>", line 496, in render
File "<string>", line 589, in get_term_size
OSError: [Errno 25] Inappropriate ioctl for device
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<string>", line 498, in render
File "<string>", line 589, in get_term_size
OSError: [Errno 25] Inappropriate ioctl for devicee[0m
This is my env: SHELL=/bin/bash SESSION_MANAGER=local/debian:@/tmp/.ICE-unix/1008,unix/debian:/tmp/.ICE-unix/1008 QT_ACCESSIBILITY=1 COLORTERM=truecolor XDG_MENU_PREFIX=gnome- TERM_PROGRAM_VERSION=1.40.1 GNOME_DESKTOP_SESSION_ID=this-is-deprecated SSH_AUTH_SOCK=/run/user/1000/keyring/ssh DESKTOP_SESSION=gnome NO_AT_BRIDGE=1 GTK_MODULES=gail:atk-bridge XDG_SEAT=seat0 PWD=/space/mars/xv6-public XDG_SESSION_DESKTOP=gnome LOGNAME=mdddd XDG_SESSION_TYPE=wayland GJS_DEBUG_TOPICS=JS ERROR;JS LOG GDM_LANG=en_US.UTF-8 HOME=/home/mdddd USERNAME=mdddd LANG=en_US.UTF-8 XDG_CURRENT_DESKTOP=GNOME WAYLAND_DISPLAY=wayland-0 CHROME_DESKTOP=code-url-handler.desktop GJS_DEBUG_OUTPUT=stderr XDG_SESSION_CLASS=user TERM=xterm-256color USER=mdddd DISPLAY=:0 SHLVL=1 XDG_VTNR=2 XDG_SESSION_ID=2 XDG_RUNTIME_DIR=/run/user/1000 XDG_DATA_DIRS=/home/mdddd/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/ PATH=/home/mdddd/.local/bin:/home/mdddd/.local/bin:/home/mdddd/bin:/home/mdddd/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games GDMSESSION=gnome DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus GIO_LAUNCHED_DESKTOP_FILE_PID=3600 GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/code.desktop TERM_PROGRAM=vscode _=/usr/bin/env
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
The fix should avoid that error but I repeat that IMHO what you’re trying to do is not a reasonable setup.
Different implementations of the “DebugConsole”? I don’t know, I’m not a vscode user myself, let me try to reproduce this…