|
From: Craig M. <cma...@ki...> - 2007-01-10 21:17:50
|
Hi all. I'd like to debug a program which needs to take an input script via stdin and was wondering what the best way to go about doing an interactive valgrind session would be (thus my earlier post). The program closes stdin after its done reading the script which is apparently why valgrind wasn't pausing at the interactive prompts. Noticed that there is an "--input-fd" option so as to take input from somewhere other than stdin. Could someone give me a real world example of how to use this so that I could redirect a file to the program's stdin, but still enter commands interactively at the valgrind prompt? Thanks, Craig ------------------------------------------------------ Craig Maloney http://www.pha.jhu.edu/~cmaloney/ |