Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[VPP-1492] Session Unit Test crash on ARM Ubuntu 1804 #285

Closed
vvalderrv opened this issue Jan 6, 2025 · 0 comments
Closed

[VPP-1492] Session Unit Test crash on ARM Ubuntu 1804 #285

vvalderrv opened this issue Jan 6, 2025 · 0 comments

Comments

@vvalderrv
Copy link
Contributor

Session Unit Tests result in crash:
==============================================================================
Session Unit Tests Case
==============================================================================
02:22:49,744 Child test runner process unresponsive and core-file exists in test temporary directory (last test running was `Session Unit Tests' in `/tmp/vpp-unittest-TestSessionUnitTests-X7zgLf')!
02:22:49,749 Creating a link to the failed test: /tmp/vpp-failed-unittests/vpp-unittest-TestSessionUnitTests-X7zgLf-FAILED -> vpp-unittest-TestSessionUnitTests-X7zgLf
02:22:49,750 Core-file exists in test temporary directory: /tmp/vpp-unittest-TestSessionUnitTests-X7zgLf/core!
02:22:49,786 Copying api_post_mortem.65481 to /tmp/vpp-unittest-TestSessionUnitTests-X7zgLf
VPP core detected in /tmp/vpp-unittest-TestSessionUnitTests-X7zgLf. Last test running was 'Session Unit Tests' (test_session.TestSessionUnitTests.test_session)

The problem is with VPP trying to access inaccessible memory:
(gdb)
#10 0x0000ffff50726cf0 in stream_session_is_valid (si=0,
thread_index=210 '\322')
at /home/jlinkes/vpp/src/vnet/session/session.h:324
324 s = pool_elt_at_index (session_manager_main.wrk[thread_index].sessions, si);
(gdb) p session_manager_main.wrk[thread_index].sessions
$1 = (stream_session_t *) 0x0
(gdb) p session_manager_main.wrk[thread_index].sessions[0]
Cannot access memory at address 0x0

I tried this multiple times and sometimes the address is 0x0 and sometimes it's 0x1313131313131313. It's 100% reproducible.

This patch introduced this failure: https://gerrit.fd.io/r/#/c/15733/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant