|
From: Scott M. <sm...@no...> - 2005-03-14 22:40:00
|
Hi, We're seeing very odd behaviour post-execution. Once Valgrind finishes it's run, any text we type at the prompt is invisible. The commands still execute ok, and we see their output, but no STDIN. This can be fixed by opening a csh and immediately exiting. Very weird. Hoping someone has seen this before and knows what's going on! Thx in advance, Scott. |
|
From: Robert W. <rj...@du...> - 2005-03-14 23:30:08
|
> We're seeing very odd behaviour post-execution. Once Valgrind finishes > it's run, any text we type at the prompt is invisible. The commands > still execute ok, and we see their output, but no STDIN. > > This can be fixed by opening a csh and immediately exiting. Very weird. > > Hoping someone has seen this before and knows what's going on! > > Thx in advance, > Scott. Sounds like noecho is getting twiddled on. Is your program a text-based UI program - i.e. does use curses or terminfo or something? It could be exiting weirdly when run under Valgrind and not setting the terminal back into shape properly. Regards, Robert. |
|
From: Dennis L. <pla...@in...> - 2005-03-14 23:57:53
|
Am Montag, den 14.03.2005, 17:39 -0500 schrieb Scott Mills: > Hi, > > We're seeing very odd behaviour post-execution. Once Valgrind finishes > it's run, any text we type at the prompt is invisible. The commands > still execute ok, and we see their output, but no STDIN. > > This can be fixed by opening a csh and immediately exiting. Very > weird. > > Hoping someone has seen this before and knows what's going on! > > Thx in advance, > Scott. Is this on every program ? Or only on ncurses/readline using programs ? Perhaps valgrind trashes the console, does the "reset" cmd do anything useful ? |