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 50751 in oss-fuzz: elfutils: Fuzzing build failure
Date: Mon, 29 Aug 2022 11:30:24 -0700	[thread overview]
Message-ID: <0000000000000c402905e7657526@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=8e49a737cfc19d839ab9a7e5b657b3e1=oss-fuzz@monorail-prod.appspotmail.com>

Status: New
Owner: ----
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com 
Labels: Proj-elfutils
Type: Build-Failure

New issue 50751 by ClusterFuzz-External: elfutils: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50751

The last 3 builds for elfutils have been failing.
Build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-093f350e-d0a5-4bf2-8bd4-b1eb1d7d10ac.txt
Build type: fuzzing

To reproduce locally, please see: https://google.github.io/oss-fuzz/advanced-topics/reproducing#reproducing-build-failures

This bug tracker is not being monitored by OSS-Fuzz team. If you have any questions, please create an issue at https://github.com/google/oss-fuzz/issues/new.

**This bug will be automatically closed within a day once it is fixed.**

-- 
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-08-29 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=8e49a737cfc19d839ab9a7e5b657b3e1=oss-fuzz@monorail-prod.appspotmail.com>
2022-08-29 18:30 ` ClusterFuzz-External via monorail [this message]
2022-08-30  0:30 ` 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=0000000000000c402905e7657526@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).