Ash shell character corrupted after gdbserver

Shell Programming and Scripting
1

I am trying to debug something using gdbserver, after the successful/YET REALLY SLOW debug session i see that the ash shell on the the target under debug is messed up.

Probably because gdbserver tries to open the core file which is binary. How do i recover from it?

Also any ideas to speed up gdbserver? i am using target remote /dev/ttyS0:wall:

2

You might prevent the core file, like with

>core ; chmod 000 core

Do you really need a debugger? I have been happy with robust code, debug messages and truss/tusc/strace for years.

3

To recover from shell corruption, try reset . Once the screen goes blank, hit enter to get a new prompt.