Re: [Valgrind-users] Unique log filename

[Skarakis, K. <kon...@un...>]

That's fantastic. Thank you very much for your time. It works great. 

Here's how I am using it:

I have this line in my ~/.valgrindrc:

--log-file=/software/valgrind/rpts/%s{"/software/dstring"}-%p-report.txt

And these are the contents of /software/dstring:

echo $(ps -f $PPID | tail -n 1 | awk "{print \$10}")-$(date +%Y%m%d%H%M%S%N)

This results in this very nice log:

$ valgrind ls
cap.cap  cov  covfsn  md5r  rpts  rpts1  rpts_fsn_errors

$ ls /software/valgrind/rpts    
ls-20140925123940975544578-18453-report.txt


Kind Regards,
Costas


------------------------------

Message: 3
Date: Wed, 24 Sep 2014 09:51:38 -0400
From: Eliot Moss <mo...@cs...>
Subject: Re: [Valgrind-users] Unique log filename
To: "val...@li..."
	<val...@li...>
Message-ID: <542...@cs...>
Content-Type: text/plain; charset="windows-1252"

On 9/24/2014 7:39 AM, Eliot Moss wrote:
> On 9/24/2014 5:31 AM, Skarakis, Konstantinos wrote:

Ok -- I decided to just give it a try in a copy of valgrind updated to svn head.  The issue is that I was temporarily sticking a null character into the format string, yet the format string was declared somewhere else as const.  That declaration was righteous, and my temporary insertion of a null I admit was a hack.  I was already copying the relevant part of the format string out into a temporary buffer, so the actual adjustments needed were small.  Once I made those changes, it compiles and passes check tests for me (on a linux amd64 system).  I attach the updated patch.  I'll see about submitting this, though there also needs to be an update to a section of the manual for a complete patch to make sense for the distro.

Regards -- Eliot Moss