https://bugs.kde.org/show_bug.cgi?id=404843
Bug ID: 404843
Summary: s390x: backtrace sometimes ends prematurely
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Sometimes Valgrind cannot unwind the stack correctly on s390x.
For instance, consider this program:
int fun_b(int *p) { return *p; }
int fun_a(int *p) { return fun_b(p); }
int main() { return fun_a(0); }
when compiling with gcc 8.0.1 and running under Valgrind, the backtrace looks
like this:
==100497== at 0x1000516: fun_b (in /home/arnez/tmp/backtrace-test)
==100497== by 0x1000551: fun_a (in /home/arnez/tmp/backtrace-test)
==100497== by 0x4866107: ??? (in /usr/lib64/libc-2.27.so)
Note that "main" is missing from the backtrace.
This problem also affects various test cases in Valgrind's test suite.
--
You are receiving this mail because:
You are watching all bug changes.
