|
From: Julian S. <js...@ac...> - 2006-03-26 21:57:18
|
Hi Without understanding all the ins and outs of this .. can you get any mileage out of the --input-fd= flag? J On Sunday 26 March 2006 22:40, Paul Walker wrote: > Hi all, > > I've been trying to confirm whether something's a bug or not in a program > which uses ncurses (mutt). I was trying to get valgrind to automatically > attach gdb when it spots the overrunning read - however, since mutt starts > up ncurses, that interferes with valgrind's input. > > I wrote a small wrapper program which accepts a telnet connection and then > forks valgrind, using the telnet connection for valgrind i/o. That seems to > work, except when it comes to starting gdb - there's no sign of it starting > at all. > > What does the gdb process that valgrind spawns use as it's stdin and > stdout? Are they dup'ed from the input-fd and log-fd, or the program's > stdin/stdout? > > I noticed various messages (at User level) in valgrind which might at least > confirm whether gdb is being started or not, but I can't seem to work out > how to turn those on... > > Any offers...? > > Thanks all, |