|
From: Paul W. <pa...@bl...> - 2006-03-26 22:06:21
|
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.
Don't suppose you remember how I can get valgrind to output this line?
[m_debugger.c]
VG_(message)(Vg_UserMsg, "starting debugger with cmd: %s", buf);
Just adding more -v options doesn't seem to have done it, unfortunately.
Cheers,
--
Paul
A debugged program is one for which you have not yet found the conditions
that make it fail. -- Jerry Ogdin
|