Add an openjpeg libfuzzer.

Add an openjpeg libfuzzer.

BUG=591789
R=tsepez@chromium.org

Committed: https://pdfium.googlesource.com/pdfium/+/bf067b461368abf7303a1285183128790134b169

[Oliver Chang, 2016-03-18 19:45:15]

Description was changed from

==========
Add an openjpeg libfuzzer.

BUG=591789
==========

to

==========
Add an openjpeg libfuzzer.

BUG=591789
==========

[Oliver Chang, 2016-03-18 19:45:15]

ochang@chromium.org changed reviewers:
+ tsepez@chromium.org

[Oliver Chang, 2016-03-18 19:45:24]

Tom, ptal. Based this on CPDF_DIBSource::LoadJpxBitmap

[Tom Sepez, 2016-03-18 20:33:41]

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/BUILD.gn
File testing/libfuzzer/BUILD.gn (right):

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/BUILD...
testing/libfuzzer/BUILD.gn:50: source_set("pdf_jpx_fuzzer") {
Need to make this linux only?

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/fuzze...
File testing/libfuzzer/fuzzers.gyp (right):

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/fuzze...
testing/libfuzzer/fuzzers.gyp:65: 'targets': [
need to test for xfa enabled?

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/pdf_j...
File testing/libfuzzer/pdf_jpx_fuzzer.cc (right):

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/pdf_j...
testing/libfuzzer/pdf_jpx_fuzzer.cc:45: bitmap->Clear(0xFFFFFFFF);
Do we have to do this? We're not going to look at the output -- does any part of
the rendering path depend upon the initial bitmap content?  Otherwise, maybe we
can save some cycles.

[Oliver Chang, 2016-03-18 20:50:26]

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/BUILD.gn
File testing/libfuzzer/BUILD.gn (right):

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/BUILD...
testing/libfuzzer/BUILD.gn:50: source_set("pdf_jpx_fuzzer") {
On 2016/03/18 20:33:40, Tom Sepez wrote:
> Need to make this linux only?  

Chromium's GN configs should handle this.

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/fuzze...
File testing/libfuzzer/fuzzers.gyp (right):

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/fuzze...
testing/libfuzzer/fuzzers.gyp:65: 'targets': [
On 2016/03/18 20:33:40, Tom Sepez wrote:
> need to test for xfa enabled?

This shouldn't depend on any XFa features.

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/pdf_j...
File testing/libfuzzer/pdf_jpx_fuzzer.cc (right):

https://codereview.chromium.org/1814223003/diff/20001/testing/libfuzzer/pdf_j...
testing/libfuzzer/pdf_jpx_fuzzer.cc:45: bitmap->Clear(0xFFFFFFFF);
On 2016/03/18 20:33:40, Tom Sepez wrote:
> Do we have to do this? We're not going to look at the output -- does any part
of
> the rendering path depend upon the initial bitmap content?  Otherwise, maybe
we
> can save some cycles.

Probably not, it would seem logical that it doesn't, but I wasn't sure if there
was some craziness happening somewhere that depended on this.

I'll remove it for now.

[Tom Sepez, 2016-03-18 22:28:27]

lgtm

[Oliver Chang, 2016-03-18 23:45:38]

Description was changed from

==========
Add an openjpeg libfuzzer.

BUG=591789
==========

to

==========
Add an openjpeg libfuzzer.

BUG=591789
R=tsepez@chromium.org

Committed:
https://pdfium.googlesource.com/pdfium/+/bf067b461368abf7303a1285183128790134...
==========

[Oliver Chang, 2016-03-18 23:45:41]

Committed patchset #3 (id:40001) manually as
bf067b461368abf7303a1285183128790134b169 (presubmit successful).