On 9/23/2014 10:11 AM, Skarakis, Konstantinos wrote:
> Hello,
>
> I want to run a big project over a long time under Valgrind’s Memcheck. I am
> using --log-file in
> conjunction with %p to generate log files per process ID. This means that
> over time I will start
> losing log files due to PID reuse. Is there a way to make my logs unique so
> that they will not be
> overwritten? Maybe some way to get a timestamp in the filename? I know that
> the only other available
> specifier is %q, but I haven’t found a way to make this work.
>
> I am running on Suse Linux 64bit.
>
> Thanks,
>
> Costas
Dear Costas -- I am not aware of anything to do that, but a while back
I wrote a patch that allows an additional format specifier, %s{....}
which runs a script and argument that are specified in the {....},
and the result of that script is used as the file name for the log
file. It would be easy enough, given that functionality, to write
a script that returns a time stamp. I will see if I can narrow this
down to a small patch that I can submit, and when I do, I can email
you the patch at the same time. I did this a while ago, but if this
part of the code has not been changed a lot, then the patch should
not be too bad to extract.
I've been meaning to submit it for some time, actually, and this is
a good prompt to make me do it!
Regards -- Eliot Moss
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
