"Raw mode" (no artificial commands) support
- Dominant language
- TypeScript
- Stars
- 10.4k
- Forks
- 521
- PR merge metrics
- No merged PRs in 30d
Description
When I am using gdbgui to debug Linux kernel remotely, I noticed that gdbgui will cause some exceptions (pasted at the end of this issue) for some reason. And looks like the reason is that those artifact commands are causing the issue.
Hence I am requesting raw mode - when this mode is enabled, no artificial commands will be sent.
This mode may prevent some features working properly (those need artificial commands to work) and it is acceptable.
================= Pasted Log ======================
No gdb response received after 10 seconds.
Possible reasons include:
1) gdbgui, gdb, or the debugged process is not running.
2) gdb or the inferior process is busy running and needs to be interrupted (press the pause button up top).
3) Something is just taking a long time to finish and respond back to this browser window, in which case you can just keep waiting.
Contributor guide
Research direction
Start by tracing how gdbgui sends artificial commands to remote GDB during Linux-kernel debugging; the issue names no files or tests. Done means an explicit raw mode prevents those commands while documenting or verifying which dependent features may stop working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, typescript
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100