summaryrefslogtreecommitdiffstats
path: root/breakpad/README.chromium
diff options
context:
space:
mode:
authorglider@chromium.org <glider@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-05-19 10:31:00 +0000
committerglider@chromium.org <glider@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-05-19 10:31:00 +0000
commita5b7b7d090670613f099b13f2edd341ed0ae0267 (patch)
treed5fc321019ad2246419edf9700e3a9abdafb2940 /breakpad/README.chromium
parentfd1cc5a88f528d58d311b24bf2b1b9b437369b30 (diff)
downloadchromium_src-a5b7b7d090670613f099b13f2edd341ed0ae0267.zip
chromium_src-a5b7b7d090670613f099b13f2edd341ed0ae0267.tar.gz
chromium_src-a5b7b7d090670613f099b13f2edd341ed0ae0267.tar.bz2
Re-land http://codereview.chromium.org/6869009 (except for the suppressions)
Introduce the ANNOTATE_LEAKING_OBJECT_PTR annotation that can be used to mark heap allocated objects as intentionally leaked ones. Annotate the histograms produced by {Histogram,BooleanHistogram,LinearHistogram,CustomHistogram}::FactoryGet(), as leaked. Rename StatsHistogram::StatsHistogramFactoryGet to StatsHistogram::FactoryGet, annotate the result as leaky. The previous commit broke the build on Linux Heapcheck, but looks like the problem has gone now. TBR=jar,willchan BUG=79322 Review URL: http://codereview.chromium.org/7048005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85898 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'breakpad/README.chromium')
0 files changed, 0 insertions, 0 deletions