[libfuzzer] improving gfx_png_image_fuzzer

[libfuzzer] improving gfx_png_image_fuzzer

- actually parsing png data
- png dictionary

BUG=584819
Committed: https://crrev.com/6d2e534692c63ff54204d3b877ef51762332ad54
Cr-Commit-Position: refs/heads/master@{#383845}

[aizatsky, 2016-03-29 20:56:32]

Description was changed from

==========
[libfuzzer] improving gfx_png_image_fuzzer

- actually parsing png data
- png dictionary

BUG=584819
==========

to

==========
[libfuzzer] improving gfx_png_image_fuzzer

- actually parsing png data
- png dictionary

BUG=584819
==========

[aizatsky, 2016-03-29 20:56:32]

aizatsky@chromium.org changed reviewers:
+ mmoroz@chromium.org, ochang@chromium.org

[Oliver Chang, 2016-03-29 21:01:36]

lgtm

[aizatsky, 2016-03-29 21:07:10]

The CQ bit was checked by aizatsky@chromium.org

[commit-bot: I haz the power, 2016-03-29 21:07:51]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1839203002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1839203002/1

[commit-bot: I haz the power, 2016-03-29 22:11:58]

Description was changed from

==========
[libfuzzer] improving gfx_png_image_fuzzer

- actually parsing png data
- png dictionary

BUG=584819
==========

to

==========
[libfuzzer] improving gfx_png_image_fuzzer

- actually parsing png data
- png dictionary

BUG=584819
==========

[commit-bot: I haz the power, 2016-03-29 22:11:59]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-29 22:13:02]

Description was changed from

==========
[libfuzzer] improving gfx_png_image_fuzzer

- actually parsing png data
- png dictionary

BUG=584819
==========

to

==========
[libfuzzer] improving gfx_png_image_fuzzer

- actually parsing png data
- png dictionary

BUG=584819

Committed: https://crrev.com/6d2e534692c63ff54204d3b877ef51762332ad54
Cr-Commit-Position: refs/heads/master@{#383845}
==========

[commit-bot: I haz the power, 2016-03-29 22:13:03]

Patchset 1 (id:??) landed as
https://crrev.com/6d2e534692c63ff54204d3b877ef51762332ad54
Cr-Commit-Position: refs/heads/master@{#383845}

[mmoroz, 2016-03-31 13:42:03]

Can we disable logging there anyhow
https://code.google.com/p/chromium/codesearch#chromium/src/ui/gfx/image/image...
?

It seems for me that those lines
(https://code.google.com/p/chromium/codesearch#chromium/src/base/logging.h&sq=...)
are mixed up. FATAL is more silent level than ERROR, so I guess ERROR should be
default for debug and FATAL default for release. Is it possible?

[mmoroz, 2016-03-31 14:12:21]

On 2016/03/31 13:42:03, mmoroz wrote:
> Can we disable logging there anyhow
>
https://code.google.com/p/chromium/codesearch#chromium/src/ui/gfx/image/image...
> ?
> 
> It seems for me that those lines
>
(https://code.google.com/p/chromium/codesearch#chromium/src/base/logging.h&sq=...)
> are mixed up. FATAL is more silent level than ERROR, so I guess ERROR should
be
> default for debug and FATAL default for release. Is it possible?

However, logging::SetMinLogLevel(logging::LOG_FATAL); disabled that, I'll upload
a CL.