You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even applying a slightly modified version of PR #109101, the failures aren't fixed. Looking closer, the weird thing is that the faulting address is reported at the very top (or bottom) of the address space, outside of the stack allocation that can be seen with pmap -x.
E.g. for Posix/stack-overflow.cpp, I see
ERROR: AddressSanitizer: SEGV on unknown address 0xfffffff4 (pc 0x70125064 bp 0x00000000 sp 0xff50bf40 T0)
thus this is not treated as a stack overflow. This matches that strace reports:
When enabling ASan SPARC testing as per PR llvm#107405, 3 stack overflow tests
`FAIL` on Linux/sparc64:
```
AddressSanitizer-sparc-linux :: TestCases/Linux/stack-overflow-recovery-mode.cpp
AddressSanitizer-sparc-linux :: TestCases/Linux/stack-overflow-sigbus.cpp
AddressSanitizer-sparc-linux :: TestCases/Posix/stack-overflow.cpp
AddressSanitizer-sparc-linux-dynamic :: TestCases/Linux/stack-overflow-recovery-mode.cpp
AddressSanitizer-sparc-linux-dynamic :: TestCases/Linux/stack-overflow-sigbus.cpp
AddressSanitizer-sparc-linux-dynamic :: TestCases/Posix/stack-overflow.cpp
```
However, as detailed in Issue llvm#109771, even a Linux equivalent of the
Solaris/sparcv9 fix (PR llvm#109101) doesn't improve the situation.
Therefore this patch `XFAIL`s the tests until the root cause can be figured
out.
Tested on `sparc64-unknown-linux-gnu`, `sparcv9-sun-solaris2.11`, and
`x86_64-pc-linux-gnu`.
When enabling ASan SPARC testing as per PR #107405, 3 stack overflow
tests `FAIL` on Linux/sparc64:
```
AddressSanitizer-sparc-linux :: TestCases/Linux/stack-overflow-recovery-mode.cpp
AddressSanitizer-sparc-linux :: TestCases/Linux/stack-overflow-sigbus.cpp
AddressSanitizer-sparc-linux :: TestCases/Posix/stack-overflow.cpp
AddressSanitizer-sparc-linux-dynamic :: TestCases/Linux/stack-overflow-recovery-mode.cpp
AddressSanitizer-sparc-linux-dynamic :: TestCases/Linux/stack-overflow-sigbus.cpp
AddressSanitizer-sparc-linux-dynamic :: TestCases/Posix/stack-overflow.cpp
```
However, as detailed in Issue #109771, even a Linux equivalent of the
Solaris/sparcv9 fix (PR #109101) doesn't improve the situation.
Therefore this patch `XFAIL`s the tests until the root cause can be
figured out.
Tested on `sparc64-unknown-linux-gnu`, `sparcv9-sun-solaris2.11`, and
`x86_64-pc-linux-gnu`.
With ASan SPARC testing enabled as per PR #107405, several stack overflow tests
FAIL
on Linux/sparc64:Even applying a slightly modified version of PR #109101, the failures aren't fixed. Looking closer, the weird thing is that the faulting address is reported at the very top (or bottom) of the address space, outside of the stack allocation that can be seen with
pmap -x
.E.g. for
Posix/stack-overflow.cpp
, I seethus this is not treated as a stack overflow. This matches that strace reports:
I don't really know what to make of this. @glaubitz
The text was updated successfully, but these errors were encountered: