KeyboardInterrupt breaks the shell formatting

[sashanicolas]

When a backtrace print is too long, it will ask if you wanna continue printing or quit, this is normal behavior of GDB. Although if you interrrupt with Ctrl+C it will generate an exception which seems not being caught properly and therefore not resetting the colors and format of the shell. Leaving the letters bold and white.

[daskol]

Could you attach screenshot, stacktrace, or whatever?

[sashanicolas]

I'm attaching a very small screenshot cause I don't want to reveal some directories (for security). But you can see how the terminal color and format change in the first image, when I pressed Ctrl+C after one or two ENTER to print more of the stack. Note that (gdb) should be printed as the bottom terminal. In the second image, when I finish printing the full backtrace, it correctly sets the colors and format back.

Each image is a screenshot of the bottom and the top of two terminal windows, so one can compare the default colors.

[sashanicolas]

Also this filter is great, so useful. Another thing, but this is as improvement. The colors should not be hard coded, as if you change the terminal colors you might not be able to read the white in a white background, or the other colors depending on the background color.

Cheers!

[daskol]

The issue is due to gdb page lister which is less on default. The issue is that gdb slices colored output by bytes and it is not aware of escape sequencies in output. I will try to figure out solution.

Thank you!