|
From: Tom H. <to...@co...> - 2006-03-26 22:59:45
|
In message <200...@bl...>
Paul Walker <pa...@bl...> wrote:
> On Sun, Mar 26, 2006 at 10:57:00PM +0100, Julian Seward wrote:
>
> > Without understanding all the ins and outs of this .. can you
> > get any mileage out of the --input-fd= flag?
>
> Sorry, I think I wasn't clear - I'm already using the input-fd and log-fd
> descriptors for valgrind input/output, and they're most useful.
>
> Since asking the question, I've even found a script from someone which pops
> up a new xterm with gdb loaded, but it never seems to fire. Maybe the 'y' is
> getting eaten somewhere en-route... this would seem to make it my problem
> rather than anything else, though.
If you're using curses and typing 'y' doesn't appear to work then
you are probably in raw mode and the return key is not doing what
valgrind expects. Try typing ctrl-J and/or ctrl-M after the y.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|