From: ClusterFuzz-External via monorail <monorail+v2.382749006@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 49759 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
Date: Wed, 03 Aug 2022 08:36:46 -0700 [thread overview]
Message-ID: <00000000000035b19005e55800c5@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=5c87152e9430b072aca8c9a404b757ed=oss-fuzz@monorail-prod.appspotmail.com>
Status: New
Owner: ----
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com
Labels: ClusterFuzz Reproducible Engine-libfuzzer OS-Linux Proj-elfutils Reported-2022-08-03
Type: Bug
New issue 49759 by ClusterFuzz-External: elfutils:fuzz-libelf: Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49759
Detailed Report: https://oss-fuzz.com/testcase?key=4741251823435776
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type: libfuzzer_asan_i386_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs)
Crash Address:
Crash State:
fuzz-libelf
Sanitizer: address (ASAN)
Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_i386_elfutils&range=202203290604:202203291200
Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4741251823435776
Issue filed automatically.
See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
* mention the fix revision(s).
* state whether the bug was a short-lived regression or an old bug in any stable releases.
* add any other useful information.
This information can help downstream consumers.
If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.
--
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 parent reply other threads:[~2022-08-03 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=5c87152e9430b072aca8c9a404b757ed=oss-fuzz@monorail-prod.appspotmail.com>
2022-08-03 15:36 ` ClusterFuzz-External via monorail [this message]
2022-11-18 15:38 ` 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=00000000000035b19005e55800c5@google.com \
--to=monorail+v2.382749006@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).