[llvm-bugs] Issue 20204 in oss-fuzz: llvm:llvm-isel-fuzzer--wasm32-O2: ASSERT: FrameBaseLocal != -1U && "Frame base local hasn't been set"

[ClusterFuzz-External via monorail via llvm-bugs]

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
igm... at gmail.com, davg at google.com, mitchp at google.com,  
bigchees... at gmail.com, eneyman at google.com, llvm-b... at lists.llvm.org,  
jfb at chromium.org, v... at apple.com, mitchphi... at outlook.com,  
xpl... at gmail.com, akils... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-01-18
Type: Bug

New issue 20204 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--wasm32-O2:  
ASSERT: FrameBaseLocal != -1U && "Frame base local hasn't been set"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20204

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
   FrameBaseLocal != -1U && "Frame base local hasn't been set"
   llvm::WebAssemblyFrameLowering::getDwarfFrameBase
   llvm::DwarfCompileUnit::updateSubprogramScopeDIE

Sanitizer: memory (MSAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=202001171840:202001180521

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

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/20200118/384364c0/attachment.html>