public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: ClusterFuzz-External via monorail <monorail+v2.382749006@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 53588 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
Date: Sun, 20 Nov 2022 07:52:48 -0800	[thread overview]
Message-ID: <0000000000003ffa4d05ede8ee4c@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=05a7693c530c7ea0e85624940e95e7d5=oss-fuzz@monorail-prod.appspotmail.com>

[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]

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-11-20
Type: Bug

New issue 53588 by ClusterFuzz-External: elfutils:fuzz-libelf: Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53588

Detailed Report: https://oss-fuzz.com/testcase?key=5208347720941568

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=202203161800:202203170000

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5208347720941568

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.

           reply	other threads:[~2022-11-20 15:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <0=71cc74a7ba1af446b7ed6b9a08b414d9=05a7693c530c7ea0e85624940e95e7d5=oss-fuzz@monorail-prod.appspotmail.com>]

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=0000000000003ffa4d05ede8ee4c@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).