Comment #7 on issue 15771 by [email protected]: valgrind_analyze.py
unhappy while parsing valgrind xml output
http://code.google.com/p/chromium/issues/detail?id=15771
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=20024
------------------------------------------------------------------------
r20024 | [email protected] | 2009-07-07 07:00:59 -0700 (Tue, 07 Jul 2009) |
11 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/process_util_posix.cc?r1=20024&r2=20023
M
http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/valgrind_test.py?r1=20024&r2=20023
Fix tools/valgrind/chrome_tests.sh to always use --log-file option
so fork() doesn't corrupt log files; lets --generate_suppressions
work even with the hacky valgrind fix that makes anything but --log-file
crash on child of fork().
Also avoid killing user desktop session if zygote dies!
BUG=none, but related to fix for http://crbug.com/15771
TEST=patch valgrind with fork workaround; sh tools/valgrind/chrome_tests.sh
--generate_suppressions -t ui logs you out on linux without this.
Review URL: http://codereview.chromium.org/155130
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
