[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gawk: invalid read and write
|
From: |
Andrew J. Schorr |
|
Subject: |
Re: gawk: invalid read and write |
|
Date: |
Sun, 28 Jan 2007 11:24:42 -0500 |
|
User-agent: |
Mutt/1.4.2.1i |
On Sat, Jan 27, 2007 at 12:07:45PM -0500, Andrew J. Schorr wrote:
> How about adding a 'valgrind-scan' target to examine the valgrind
> log files for problems? Something like the attached patch?
Hmmm, my patch assumes the log files match this shell pattern: log.[0-9]*.
But I just realized that older versions of valgrind (e.g. 2.4.1)
use a different naming convention: log.pid[0-9]*. Is it worth
changing the patch to support the older valgrind?
Regards,
Andy