News for hackers. Stuff that matters.
Re:The State of Linux Debuggers by db48x on Sunday December 13, 2020 @10:32AM (#25407204)
The rendering problems in curses programs could easily be the fault of his terminal emulator or even an incorrect value in his TERM variable.
Re:The State of Linux Debuggers by tehnicaorg on Sunday December 13, 2020 @11:10AM (#25407516)
Is there an easy way to check if everything is set up properly and also to get tips on what needs to be changed?
Re:The State of Linux Debuggers by db48x on Sunday December 13, 2020 @03:50PM (#25410119)
Not really, but the most common mistake is to set TERM in your shell startup files (.bashrc, for example). If you do that, then you could end up setting it to a value not supported by your terminal emulator. If you don't set it, then your terminal emulator will set it to an appropriate value for you.
Re:The State of Linux Debuggers by xioxox on Sunday December 13, 2020 @11:29AM (#25407691)
I thought one needed Ctrl+L to refresh the screen when it gets corrupted by program output in "gdb -tui".
Re:The State of Linux Debuggers by db48x on Sunday December 13, 2020 @03:49PM (#25410107)
That's absolutely true, I'd forgotten about that. It's hard to tell from the screenshot if that's what happened, but it's quite likely.