Automatically applying components based on crash stacktrace and information from OWNERS files.
If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e3140a8f27345d395ea75fe619d730951a438e89 (Run SQLite DBFuzz2 on ClusterFuzz to fuzz for data corruption).
If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Nope, the problem is still there.
Richard and Dan, could you please take a look?
dbfuzz2 test case attached. Stack trace below.
Note that we've landed a bunch of backported patches, so the sqlite3.c file that you've downloaded yesterday is no longer valid. You'll have to download it again. The most recent version of https://cs.chromium.org/codesearch/f/chromium/src/third_party/sqlite/amalgamation/sqlite3.c should have a SHA1 of f596d00570b4c80e3b3c7ed058602f5a754bada8
==3763083==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x5600f9615af8 bp 0x7fff6c798e90 sp 0x7fff6c798960 T0)
==3763083==The signal is caused by a READ memory access.
==3763083==Hint: address points to the zero page.
SCARINESS: 10 (null-deref)
#0 0x5600f9615af7 in sqlite3VdbeExec third_party/sqlite/amalgamation/sqlite3.c:85604:22
#1 0x5600f95ae957 in sqlite3Step third_party/sqlite/amalgamation/sqlite3.c:81444:10
#2 0x5600f95a6338 in sqlite3_step third_party/sqlite/amalgamation/sqlite3.c:81507:16
#3 0x5600f95b6ce5 in sqlite3_exec third_party/sqlite/amalgamation/sqlite3.c:118092:12
#4 0x5600f94e39f4 in LLVMFuzzerTestOneInput third_party/sqlite/src/test/dbfuzz2.c:95:5
#5 0x5600f94e44bd in ExecuteFilesOnyByOne(int, char**) third_party/libFuzzer/src/afl/afl_driver.cpp:301:5
#6 0x5600f94e4d45 in main third_party/libFuzzer/src/afl/afl_driver.cpp:339:12
#7 0x7f8b1c91b82f in __libc_start_main /build/glibc-Cl5G7W/glibc-2.23/csu/libc-start.c:291
ClusterFuzz testcase 6280052809138176 is verified as fixed, so closing issue as verified.
If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Comment 1 by ClusterFuzz
, Jan 15Labels: Test-Predator-Auto-Components