|
From: tim l. <ti...@tl...> - 2008-01-21 11:30:09
|
I have upgraded from valgrind 3.2.3 to version 3.3.0 . It will not start up now, and fails with the message valgrind: Bad option '--log-file-exactly=3D/home/tim/valgrindtrace'; aborting. valgrind: Use --help for more information. The command line is valgrind -v --log-file=3D/home/tim/valtrace ./Ports I had a ~/valgrindrc file with this option in, but after I deleted it ( the file, that is ) the error persisted. I have no other rc file, and there is no $VALGRIND_OPTS env variable. The bizarre thing is that if I run valgrind under strace, it works fine (except for too much output from strace :-( ). Any suggestions? Tim |
|
From: Ashley P. <api...@co...> - 2008-01-21 11:43:09
|
On Mon, 2008-01-21 at 12:27 +0100, tim launchbury wrote: > The bizarre thing is that if I run valgrind under strace, it works fine > (except for too much output from strace :-( ). Any suggestions? You haven't got a shell alias for valgrind setup have you, does /usr/bin/valgrind work? Ashley, |
|
From: Tim <ti...@tl...> - 2008-01-22 13:03:11
|
On Mon, 2008-01-21 at 11:43 +0000, Ashley Pittman wrote: > On Mon, 2008-01-21 at 12:27 +0100, tim launchbury wrote: > > > The bizarre thing is that if I run valgrind under strace, it works fine > > (except for too much output from strace :-( ). Any suggestions? > > You haven't got a shell alias for valgrind setup have you, > does /usr/bin/valgrind work? > > Ashley, > Thanks, that fixed it. I had forgotten that I had set up an alias Tim |
|
From: Julian S. <js...@ac...> - 2008-01-21 11:58:23
|
On Monday 21 January 2008 12:27, tim launchbury wrote: > I have upgraded from valgrind 3.2.3 to version 3.3.0 . It will not start > up now, and fails with the message > > valgrind: Bad option '--log-file-exactly=/home/tim/valgrindtrace'; > aborting. > valgrind: Use --help for more information. That message comes from 3.2.3, not 3.3.0. So I guess you haven't successfully gotten rid of 3.2.3. J |