Comment #1 on issue 45637 by da...@adalogics.com: elfutils:fuzz-libelf: Timeout
in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c1
ASAN report:
Running:
/mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-15f79e70f92567039dd67b7c3a16ad3a180b3a6e
ALARM: working on the last Unit for 61 seconds
and the timeout value is 60 (use -timeout=N to change)
==5980== ERROR: libFuzzer: timeout after 61 seconds
#0 0x52e5c1 in __sanitizer_print_stack_trace
/src/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:87:3
#1 0x46e9e8 in fuzzer::PrintStackTrace()
/src/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:5
#2 0x453db9 in fuzzer::Fuzzer::AlarmCallback()
/src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:301:5
#3 0x7f7ca26eb3bf in libpthread.so.0
#4 0x571322 in elf_cvt_Verneed /src/elfutils/libelf/version_xlate.h:211:20
#5 0x56957e in convert_data /src/elfutils/libelf/elf_getdata.c:192:7
#6 0x56957e in __libelf_set_data_list_rdlock
/src/elfutils/libelf/elf_getdata.c:453:7
#7 0x569a67 in __elf_getdata_rdlock /src/elfutils/libelf/elf_getdata.c:560:5
#8 0x569b1c in elf_getdata /src/elfutils/libelf/elf_getdata.c:578:12
#9 0x56d9d4 in elf_compress_gnu
/src/elfutils/libelf/elf_compress_gnu.c:150:24
#10 0x55dbba in fuzz_logic_one /src/fuzz-libelf.c:48:15
#11 0x55e077 in LLVMFuzzerTestOneInput /src/fuzz-libelf.c:82:3
#12 0x4553f2 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*,
unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:611:15
#13 0x440fa2 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned
long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#14 0x44680c in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char
const*, unsigned long))
/src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:9
#15 0x46f1a2 in main
/src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#16 0x7f7ca24df0b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#17 0x41f6ed in _start
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
