Bug 196537
| Summary: | [regression] since commit eab09532d400 AddressSanitizer shadow memory range interleaves with existing memory mapping | ||
|---|---|---|---|
| Product: | Other | Reporter: | Max Bruckner (max) |
| Component: | Other | Assignee: | other_other |
| Status: | NEW --- | ||
| Severity: | normal | CC: | evangelos, konstantin.s.serebryany, mail2benny, max |
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | 4.12.3 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
AddressSanitizer error message
Log of git bisect cpuinfo |
||
Created attachment 257765 [details]
Log of git bisect
Created attachment 257767 [details]
cpuinfo
Note: The offending commit has been added in 4.12.3 Issue on the AddressSanitizer GitHub issue tracker: https://github.com/google/sanitizers/issues/837 |
Created attachment 257763 [details] AddressSanitizer error message When upgrading from 4.11 to 4.12.3 suddenly AddressSanitizer stopped working. Tested with a simple hello world and compiling with clang and `-fsanitize=address`. Clang version 4.0.1. Binaries produced that way stop to work with an error message complaining that the shadow memory range interleaves with an existing memory mapping. After some investigation I started bisecting the issue and found the following commit to be the culprit: eab09532d400 binfmt_elf: use ELF_ET_DYN_BASE only for PI I'm on Intel x86_64, cpuinfo in the attachment. I didn't try on different hardware, it didn't happen in VirtualBox though but happened in QEMU + KVM.