public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
* Issue 47421 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
       [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=439c84fd83c3cf6267cb775f7a154952=oss-fuzz@monorail-prod.appspotmail.com>
@ 2022-05-12 18:40 ` ClusterFuzz-External via monorail
  2022-07-31 14:43 ` ClusterFuzz-External via monorail
  1 sibling, 0 replies; 2+ messages in thread
From: ClusterFuzz-External via monorail @ 2022-05-12 18:40 UTC (permalink / raw)
  To: elfutils-devel

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-05-12
Type: Bug

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

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

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=5573250354118656

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Issue 47421 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
       [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=439c84fd83c3cf6267cb775f7a154952=oss-fuzz@monorail-prod.appspotmail.com>
  2022-05-12 18:40 ` Issue 47421 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf ClusterFuzz-External via monorail
@ 2022-07-31 14:43 ` ClusterFuzz-External via monorail
  1 sibling, 0 replies; 2+ messages in thread
From: ClusterFuzz-External via monorail @ 2022-07-31 14:43 UTC (permalink / raw)
  To: elfutils-devel

Updates:
	Labels: ClusterFuzz-Verified
	Status: Verified

Comment #1 on issue 47421 by ClusterFuzz-External: elfutils:fuzz-libelf: Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47421#c1

ClusterFuzz testcase 5573250354118656 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_i386_elfutils&range=202207310603:202207311200

If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new

-- 
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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-07-31 14:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=439c84fd83c3cf6267cb775f7a154952=oss-fuzz@monorail-prod.appspotmail.com>
2022-05-12 18:40 ` Issue 47421 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf ClusterFuzz-External via monorail
2022-07-31 14:43 ` ClusterFuzz-External via monorail

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).