-
Notifications
You must be signed in to change notification settings - Fork 3k
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
pkt_testdriver test run fails with a segmentation fault on Debian Unstable arm64 #648
Comments
Can you run the testdriver from gdb & gather a backtrace ("where") when it crashes?
|
Sure, I will. |
As discussed in today's community meeting I'll test this immediately again and rebuild the Debian system. If the problem still exists I shall wait for a week or two. This could just be a result of a broken compiler or such which might be fixed or get a fix shortly - the packages in Debian unstable get updated very frequently. |
Rebuilding the Debian unstable arm64 container image from scratch did not help. I shall retry later. |
The failure is still present after a forced rebuild of the Debian unstable arm64 image. I'll go the gdb route. |
gdb logs:
|
As suggested by @cron2 I compiled with -O0 and then things magically started working:
|
Describe the bug
The pkt_testdriver test fails due to a segmentation fault on latest Git "master" OpenVPN on Debian Unstable arm64. This does not seem to affect the Debian Unstable on amd64.
To Reproduce
This should be reproduceable with latest Debian Unstable Docker hub container images simply by running the usual build procedure followed by "make check". Alternatively updating the Debian Unstable arm64 base image to the latest upstream (debian) version in Buildbot should trigger this behavior.
Expected behavior
The pkt_testdriver test should pass and not segfault.
Version information (please complete the following information):
Additional context
stdio.txt
The text was updated successfully, but these errors were encountered: