[llvm-bugs] Issue 3629 in oss-fuzz: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int."

[monor… via monorail via llvm-bugs]

Comment #3 on issue 3629 by  
monor... at clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Offset <=  
INT_MAX && "Offset too big to fit in int."
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3629#c3

ClusterFuzz has detected this issue as fixed in range  
201711140614:201711141648.

Detailed report: https://oss-fuzz.com/testcase?key=5184827646017536

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel
Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
   Offset <= INT_MAX && "Offset too big to fit in int."
   llvm::AArch64RegisterInfo::needsFrameBaseReg
   LocalStackSlotPass::runOnMachineFunction

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710121744:201710130152
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711140614:201711141648

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

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.

If you suspect that the result above is incorrect, try re-doing that job on  
the test case report page.

-- 
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/20171115/5fc7b020/attachment.html>