|
From: Bob R. <bo...@br...> - 2004-04-21 01:56:38
|
Hi, Is there any easy way to run valgrind on a curses application. Basically, when you tell valgrind to run a new window, is there an option to have it execute the new program in an xterm or something? That would help the I/O fighting between valgrind and the exe. Any ideas? Thanks, Bob Rossi |
|
From: Nicholas N. <nj...@ca...> - 2004-04-21 07:21:15
|
On Tue, 20 Apr 2004, Bob Rossi wrote:
> Is there any easy way to run valgrind on a curses application.
> Basically, when you tell valgrind to run a new window, is there an
> option to have it execute the new program in an xterm or something? That
> would help the I/O fighting between valgrind and the exe.
Do these options help?
--logfile-fd=<number> file descriptor for messages [2=stderr]
--logfile=<file> log messages to <file>.pid<pid>
--logsocket=ipaddr:port log messages to socket ipaddr:port
Eg.
valgrind --tool=memcheck --logfile-fd=19 ./myapp 19> myapp.out
N
|
|
From: Henrik N. <hn...@ma...> - 2004-04-22 00:51:12
|
On Tue, 20 Apr 2004, Bob Rossi wrote: > Is there any easy way to run valgrind on a curses application. > Basically, when you tell valgrind to run a new window, is there an > option to have it execute the new program in an xterm or something? That > would help the I/O fighting between valgrind and the exe. The following should work I think: exec 5>&2 xterm -e valgrind --logfile-fd=5 ... Regards Henrik |
|
From: Bob R. <bo...@br...> - 2004-04-22 02:14:09
|
On Thu, Apr 22, 2004 at 02:50:14AM +0200, Henrik Nordstrom wrote: > On Tue, 20 Apr 2004, Bob Rossi wrote: > > > Is there any easy way to run valgrind on a curses application. > > Basically, when you tell valgrind to run a new window, is there an > > option to have it execute the new program in an xterm or something? That > > would help the I/O fighting between valgrind and the exe. > > The following should work I think: > > exec 5>&2 > xterm -e valgrind --logfile-fd=5 ... Wow. I have never knew you could do that. Thanks! Bob Rossi |