Max, would you mind looking into this? Feel free to assign back to me if you're swamped with other things.

I don't mind to work on this, but probably cannot to do it very soon.

I think that we need:

1) build all fuzzers with debug and check which of them are not too noisy

2) then we probably will implement some simple white-listing and add a new configuration to build-bots

Both parts are easy, but first one may take some time since we have 80+ fuzzers.

I'll start to run locally debug builds of fuzzers in alphabetical order.

Hm, after some thinking I came to another point.

We may enable debug builds, but initially use empty while-list of fuzzers there.

Then, when somebody ensures that some fuzzer is silent enough to be fuzzed with debug build, we add it into the while-list.

So, I will start with adding new build configuration.

Sounds like a good way to get this started. Thanks, Max!

sgtm too. thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ddbb47c14321d71cfc60d6a6684ae5db4b558ffc

commit ddbb47c14321d71cfc60d6a6684ae5db4b558ffc
Author: mmoroz <mmoroz@chromium.org>
Date: Tue May 10 17:16:35 2016

[libfuzzer] Adding ASan Debug build configuration.

R=aizatsky@chromium.org, dpranke@chromium.org, ochang@chromium.org
BUG= 607627 

Review-Url: https://codereview.chromium.org/1958133002
Cr-Commit-Position: refs/heads/master@{#392634}

[modify] https://crrev.com/ddbb47c14321d71cfc60d6a6684ae5db4b558ffc/tools/mb/mb_config.pyl

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build.git/+/d11f1e908d390c8f56359121b2ca504abc2492dd

commit d11f1e908d390c8f56359121b2ca504abc2492dd
Author: mmoroz@chromium.org <mmoroz@chromium.org>
Date: Thu May 12 09:38:08 2016

[libfuzzer] Adding and registering ASan Debug build.

R=aizatsky@chromium.org, dpranke@chromium.org, ochang@chromium.org
BUG= 607627 

Review-Url: https://codereview.chromium.org/1962693002

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/build@300556 0039d316-1c4b-4281-b951-d872f2087c98

[modify] https://crrev.com/d11f1e908d390c8f56359121b2ca504abc2492dd/masters/master.chromium.fyi/master.cfg
[modify] https://crrev.com/d11f1e908d390c8f56359121b2ca504abc2492dd/masters/master.chromium.fyi/slaves.cfg
[add] https://crrev.com/d11f1e908d390c8f56359121b2ca504abc2492dd/scripts/slave/recipes/chromium_libfuzzer.expected/full_chromium_fyi_Libfuzzer_Upload_Linux_ASan_Debug.json
[modify] https://crrev.com/d11f1e908d390c8f56359121b2ca504abc2492dd/scripts/slave/recipes/chromium_libfuzzer.py

The following revision refers to this bug:
  http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=87782

------------------------------------------------------------------
r87782 | recipe-roller@chromium.org | 2016-05-12T09:42:54.005718Z

-----------------------------------------------------------------

Hmm, looks like I missed something. Both CLs have been landed, master has been restarted, but I don't see Debug builds  https://build.chromium.org/p/chromium.fyi/buildslaves/slave43-c1.

i do see builds on https://pantheon.corp.google.com/storage/browser/chromium-browser-libfuzzer/linux-debug-asan/?authuser=0 and https://build.chromium.org/p/chromium.fyi/builders/Libfuzzer%20Upload%20Linux%20ASan%20Debug

Great! Additional restart has been required (bug 610780).

Now we need to white-list fuzzers which are suitable for fuzzing with debug build. My suggestion is to use some additional environment variable for a new CF job (libfuzzer_chrome_asan_debug, isn't created yet). Something like DEBUG_FUZZERS_ENABLED=aaa_fuzzer:bbb_fuzzer:ccc_fuzzer. IMHO it would be easier to use than having a white-list in libfuzzer.py or anywhere else in the source code.

Since I'm CF sheriff now and periodically checking CF reports, I dedicated bots 246-250 for libfuzzer_chrome_asan_debug job.

Recreated only one bot (246) at the moment to see how it goes.

Looks fine, I've recreated 4 more bots (247-250).

Interesting, that debug builds are smaller than release ones, for example:

Release:
-rwxr-x--- 1 mmoroz eng 21014352 Aug 11 13:48 out/Release/icu_break_iterator_fuzzer

Debug:
-rwxr-x--- 1 mmoroz eng  2974824 Aug 11 13:59 out/Release/icu_break_iterator_fuzzer

Max, can you put this in sanitizer huge binary size bug. This bug for debug build support is done.