From: "da… via monorail" <monorail+v2.1355924921@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45635 in oss-fuzz: elfutils:fuzz-libdwfl: Timeout in fuzz-libdwfl
Date: Sun, 20 Mar 2022 03:00:37 -0700 [thread overview]
Message-ID: <00000000000094dd4305daa373c2@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=95e64ea3122ce81a9297cfc875a38700=oss-fuzz@monorail-prod.appspotmail.com>
Comment #1 on issue 45635 by da...@adalogics.com: elfutils:fuzz-libdwfl: Timeout in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45635#c1
UBSAN report
Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-2aaefec51e4f82909c4edd9ae287bf51b2eb6dd7
ALARM: working on the last Unit for 61 seconds
and the timeout value is 60 (use -timeout=N to change)
==225963== ERROR: libFuzzer: timeout after 61 seconds
#0 0x4b1a04 in __sanitizer_print_stack_trace /src/llvm-project/compiler-rt/lib/ubsan/ubsan_diag_standalone.cpp:31:3
#1 0x457028 in fuzzer::PrintStackTrace() /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:5
#2 0x43c3f9 in fuzzer::Fuzzer::AlarmCallback() /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:301:5
#3 0x7f4c926dc3bf in libpthread.so.0
#4 0x56b144 in read_long_names /src/elfutils/libelf/elf_begin.c:760:28
#5 0x56b144 in __libelf_next_arhdr_wrlock /src/elfutils/libelf/elf_begin.c:912:8
#6 0x56c6fb in dup_elf /src/elfutils/libelf/elf_begin.c:1061:10
#7 0x56c6fb in lock_dup_elf /src/elfutils/libelf/elf_begin.c:1119:10
#8 0x56c17e in elf_begin /src/elfutils/libelf/elf_begin.c:0
#9 0x4b5782 in process_archive /src/elfutils/libdwfl/offline.c:251:17
#10 0x4b5782 in process_file /src/elfutils/libdwfl/offline.c:125:14
#11 0x4b5e9f in __libdwfl_report_offline /src/elfutils/libdwfl/offline.c:287:22
#12 0x4b5e9f in dwfl_report_offline /src/elfutils/libdwfl/offline.c:316:10
#13 0x4b2f88 in LLVMFuzzerTestOneInput /src/fuzz-libdwfl.c:47:22
#14 0x43da32 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:611:15
#15 0x4295e2 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#16 0x42ee4c in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:9
#17 0x4577e2 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#18 0x7f4c924d00b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#19 0x407d2d in _start
SUMMARY: libFuzzer: timeout
--
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.
next prev parent reply other threads:[~2022-03-20 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=95e64ea3122ce81a9297cfc875a38700=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 6:44 ` ClusterFuzz-External via monorail
2022-03-20 10:00 ` da… via monorail [this message]
2022-03-20 10:01 ` da… via monorail
2022-03-22 14:26 ` ClusterFuzz-External via monorail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000094dd4305daa373c2@google.com \
--to=monorail+v2.1355924921@chromium.org \
--cc=elfutils-devel@sourceware.org \
--cc=oss-fuzz@monorail-prod.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).