summaryrefslogtreecommitdiffstats
path: root/third_party/libevent/Makefile.in
diff options
context:
space:
mode:
authortimurrrr@chromium.org <timurrrr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-12-04 17:51:40 +0000
committertimurrrr@chromium.org <timurrrr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-12-04 17:51:40 +0000
commit9b22dee4f3d8a16d9f89eb34ac023c5734474480 (patch)
treef4bfd5dd96fdc5d2f537fe97c56bf34a6718b95c /third_party/libevent/Makefile.in
parentb284843ba6a1e90c12f91eaf796726433dc2537d (diff)
downloadchromium_src-9b22dee4f3d8a16d9f89eb34ac023c5734474480.zip
chromium_src-9b22dee4f3d8a16d9f89eb34ac023c5734474480.tar.gz
chromium_src-9b22dee4f3d8a16d9f89eb34ac023c5734474480.tar.bz2
Add linux_valgrind as a default trybot for tools/valgrind/memcheck/ and third_party/tcmalloc/
Apart from annoying developers with try mail, I think this will make some allocation-related changes better tested. Also, this would help us check the correctness of suppressions (especially, if they are formatted incorrectly). TEST=try a changelist in tools/valgrind/memcheck/ or third_party/tcmalloc/ and notice linux_valgrind bot Review URL: http://codereview.chromium.org/465046 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33828 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/libevent/Makefile.in')
0 files changed, 0 insertions, 0 deletions