|
From: Alan M. <ala...@jp...> - 2013-12-20 19:14:48
|
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 | \
grep -v 'counts of detected' | grep -v 'HEAP SUMMARY' | \
grep -v checked | sed 's/==[0-9]*== //' | \
sed 's/(suppressed: [0-9]* from [0-9]*)//' >valgrind.report
On 12/20/2013 11:04 AM, David Dyck wrote:
> 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 <sa...@ya...
> <mailto:sa...@ya...>> 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
>
> ==19182== at 0x1B8FF5CD: malloc (vg_replace_malloc.c:130)
>
> ==19182== by 0x8048385: f (example.c:5)
>
> ==19182== by 0x80483AB: main (example.c:11)
>
> is not very diff-friendly. Is there a way to suppress process id
> and address printing? Perhaps something like
>
> ==?????== Invalid write of size 4
> ==?????== at 0x???????: f (example.c:6)
> ==?????== by 0x???????: main (example.c:11)
> ==?????== Address 0x??????? is 0 bytes after a block of size 40
> alloc'd
> ==?????== at 0x???????: malloc (vg_replace_malloc.c:130)
> ==?????== by 0x???????: f (example.c:5)
> ==?????== by 0x???????: main (example.c:11)
>
>
> or
> ==== Invalid write of size 4
> ==== at : f (example.c:6)
> ==== by : main (example.c:11)
> ==== Address is 0 bytes after a block of size 40 alloc'd
> ==== at : malloc (vg_replace_malloc.c:130)
> ==== by : f (example.c:5)
> ==== by : main (example.c:11)
>
>
> Or is there a better way?
>
> Thanks,
> Nick
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business.
> Most IT
> organizations don't have a clear picture of how application
> performance
> affects their revenue. With AppDynamics, you get 100% visibility
> into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
> AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> <mailto:Val...@li...>
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
|