Project

General

Profile

Actions

Bug #1353

closed

' kernel/test_callstack 11 - Validate userspace callstack' regressed between 2.13.4 and 2.13.6

Added by Alexander Kanavin almost 2 years ago. Updated almost 2 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
05/04/2022
Due date:
% Done:

0%

Estimated time:

Description

The log is

not ok 11 - Validate userspace callstack
FAIL: kernel/test_callstack 11 - Validate userspace callstack
#   Failed test 'Validate userspace callstack'
#   in ./kernel/test_callstack:test_user_callstack() at line 80.
# Kernel callstack test

Line 80 in ./tests/regression/kernel/test_callstack is:

"$BABELTRACE_BIN" "$TRACE_PATH" | grep $EVENT_NAME | ./"$PARSE_CALLSTACK" --user "$TEST_APP_USERSPACE" $USER_CS_EXPECTED
ok $? "Validate userspace callstack"

I have obtained the failing TRACE_PATH output, please see the attachment.


Files

trace-user-callstack.tar.xz (1.62 KB) trace-user-callstack.tar.xz failing TRACE_PATH output Alexander Kanavin, 05/04/2022 11:46 AM
Actions #1

Updated by Alexander Kanavin almost 2 years ago

The fuller log is:

ok 9 - Stop lttng tracing for session
PASS: kernel/test_callstack 9 - Stop lttng tracing for session
Traceback (most recent call last):
File "/usr/lib/lttng-tools/ptest/tests/regression/././kernel//../../utils/parse-callstack.py", line 160, in <module>
main()
File "/usr/lib/lttng-tools/ptest/tests/regression/././kernel//../../utils/parse-callstack.py", line 155, in main
raise Exception('Expected function name not found in recorded callstack')
Exception: Expected function name not found in recorded callstack
ok 10 - Destroy session callstack
PASS: kernel/test_callstack 10 - Destroy session callstack
not ok 11 - Validate userspace callstack
FAIL: kernel/test_callstack 11 - Validate userspace callstack
  1. Failed test 'Validate userspace callstack'
  2. in ./kernel/test_callstack:test_user_callstack() at line 82.
  3. Kernel callstack test

I have one more thing to try, please hold. Maybe the problem is on our end.

Actions #2

Updated by Alexander Kanavin almost 2 years ago

The issue was that we used a stripped binary where a non-stripped one is expected. This ticket can be closed, but I do not see how.

Actions #3

Updated by Mathieu Desnoyers almost 2 years ago

  • Status changed from New to Invalid
Actions

Also available in: Atom PDF