Abrt in /usr/lib/libc++abi.dylib:x86_64 |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5612615092142080 Fuzzer: libFuzzer_pdfium_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Abrt Crash Address: 0x7fff95d8af06 Crash State: /usr/lib/libc++abi.dylib:x86_64 /usr/lib/libc++abi.dylib:x86_64 _objc_terminate Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=419764:419788 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5612615092142080 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 2 2017
ClusterFuzz testcase 5612615092142080 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Oct 2 2017
This doesn't seem like it's a PDF issues. This is crashing down in the code to build a std::string. I'm guessing (since the line numbers in the stack don't make sense, that its:
80 std::string ProgramPath() {
89 char* path = new char[PATH_MAX + 1];
90 assert(path);
91 ssize_t sz = readlink("/proc/self/exe", path, PATH_MAX);
92 assert(sz > 0);
93 std::string result(path, sz);
94 delete[] path;
95 return result;
97 }
which is crashing on line 98. The readlink method returned successfully since we assert that sz > 0, and then it crashes inside std::string result(path, sz). (At least, that's my guess).
,
Nov 7 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by kkaluri@chromium.org
, Sep 25 2017