Hello, for the Valgrind simulations inside our company I wrote a tool to
prettify/format the output from Valgrind-Memcheck logs while adding
additional information to the output
- Combines the valgrind logs from many test runs
- Aggregates multiple occurrences of issues with same stack trace
On Fri, 2013-12-20 at 21:24 +0100, Paul Floyd wrote:
> Even this is not very diff-friendly (changing line numbers will cause diffs).
>
> I recommend enabling suppression generation (--gen-suppressions=yes). Then
> you can filter anything that isn't
> between braces. Or even simply use suppressi
On 20 Dec 2013, at 19:16, Nick Savoiu wrote:
> Hi all,
>
> Valgrind's typical output
>
> ==19182== Invalid write of size 4
> ==19182==at 0x804838F: f (example.c:6)
> ==19182==by 0x80483AB: main (example.c:11)
> ==19182== Address 0x1BA45050 is 0 bytes after a block of size 40 alloc'd
/\(vg_replace_malloc.c:(\d+)\)/(vg_replace_malloc.c:XXX)/;
print;
}
-Original Message-
From: Nick Savoiu [mailto:sav...@yahoo.com]
Sent: Friday, December 20, 2013 10:17 AM
To: valgrind-users@lists.sourceforge.net
Subject: [Valgrind-users] Making valgrind output diff-friendly
Hi all,
Valgrind&
I use grep when I invoke valgrind in my makefile (where the valgrind
output from my entire regression suite is concatenated into
/tmp/valgrind.report):
grep -v STACK /tmp/valgrind.report | grep -v allocs | \
grep -v 'memory error detector' | grep -iv copyright | \
I had a similar problem, and ended up filtering all the addresses and
identifiers out, so I could to a diff.
Since sometimes address are not as important as names, I wonder what kinds
of indirection could be done to "hide" the addresses and stuff..
On Fri, Dec 20, 2013 at 10:16 AM, Nick Savoiu
Hi all,
Valgrind's typical output
==19182== Invalid write of size 4
==19182==at 0x804838F: f (example.c:6)
==19182==by 0x80483AB: main (example.c:11)
==19182== Address 0x1BA45050 is 0 bytes after a block of size 40 alloc'd
==19182==at 0x1B8FF5CD: malloc (vg_replace_malloc.
