[llvm-bugs] Issue 29925 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-O2: ASSERT: (!RS || !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out

[ClusterFuzz-External via monorail via llvm-bugs]

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevl... at apple.com, igm... at gmail.com, davg at google.com, mitchp at google.com, bigch... at gmail.com, eneyman at google.com, llvm-... at lists.llvm.org, jfb at chromium.org, v... at apple.com, mitch... at outlook.com, xpl... at gmail.com, akils... at apple.com 
Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-01-25
Type: Bug

New issue 29925 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--aarch64-O2: ASSERT: (!RS || !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=29925

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

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: llvm-isel-fuzzer--aarch64-O2
Job Type: libfuzzer_msan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  (!RS || !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out
  llvm::AArch64RegisterInfo::eliminateFrameIndex
  llvm::RegScavenger::spill
  
Sanitizer: memory (MSAN)

Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&revision=202011180625

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

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 part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20210125/7a7b8bb7/attachment-0001.html>