[Bug sanitizer/65479] New: sanitizer stack trace missing frames past #0 on powerpc64
msebor at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Thu Mar 19 23:02:00 GMT 2015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65479
Bug ID: 65479
Summary: sanitizer stack trace missing frames past #0 on
powerpc64
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
On both powerpc64 and powerpc64le, the c-c++-common/asan/misalign-1.c shows 6
failures, all in the output pattern test. The failures are due to to the stack
trace missing stack frame #1 (it only includes frame #0). It looks like the
backtrace on powerpc doesn't work correctly.
=================================================================
==87868==ERROR: AddressSanitizer: unknown-crash on address 0x3fffc231eb2f at pc
0x000010000ce8 bp 0x3fffc231e9f0 sp 0x3fffc231ea10
READ of size 4 at 0x3fffc231eb2f thread T0
#0 0x10000ce4 in foo
/src/gcc-5.0-git/gcc/testsuite/c-c++-common/asan/misalign-1.c:11
Address 0x3fffc231eb2f is located in stack of thread T0 at offset 175 in frame
#0 0x1000086c in main
/src/gcc-5.0-git/gcc/testsuite/c-c++-common/asan/misalign-1.c:28
This frame has 3 object(s):
[32, 36) 'v'
[96, 100) 'w'
[160, 176) 't' <== Memory access at offset 175 partially overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism or swapcontext
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: unknown-crash
/src/gcc-5.0-git/gcc/testsuite/c-c++-common/asan/misalign-1.c:11 foo
Shadow bytes around the buggy address:
0x09fff8463d10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463d20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463d30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463d40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463d50: f1 f1 f1 f1 04 f4 f4 f4 f2 f2 f2 f2 04 f4 f4 f4
=>0x09fff8463d60: f2 f2 f2 f2 00[00]f4 f4 f3 f3 f3 f3 00 00 00 00
0x09fff8463d70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463d80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463d90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463da0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x09fff8463db0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
==87868==ABORTING
More information about the Gcc-bugs
mailing list