-
Notifications
You must be signed in to change notification settings - Fork 273
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
Test suite "bus error" on armhf #725
Comments
Hmwait, that was actually reverted later (in 084ec86), but the test does not do the right thing on armhf (config.log):
|
After (re-)adding
Test log shows:
If you have an idea about this, I'm happy to experiment more - I failed to find the regression as unfortunately there are many commits since the 4.3.4 release that fail to build. Error message is:
|
I get my armhf image from here and cannot reproduce it. My approach will be to restore FORCE_ALIGN for non-macOS arm and get fuzzing working on armhf.
|
PR #742 This fix restores alignment for arm processors, and fixes L7 for FORCE_ALIGN builds. Although I was not able to reproduce original issues, it appears that this will fix the issue. Verification
|
Thanks, successfully tested 4.4.2-beta1 on armhf and mipsel in Debian unstable. About armhf, I reckon (but don't quote me on that) this depends on the actual CPU. Native armhf ones like Cortex-A7 do fine, but the Cortex-A72 in a Raspberry 4 (in an armhf chroot) enforces strict alignment. Unfortunately I cannot verify this, but I heard some talking of that kind. |
Very interesting. I never have been able to verify any alignment issues in my test environment, so this is good news. Maybe I should get the Cortex-A72 chroot environment. I am waiting for news on #724 to determine if it is a bug or a feature. If it is a feature, I will push it out to 4.5 and release 4.4.2. In any case, fix should be GA within the next couple weeks. |
Restore old setting that sets FORCE_ALIGN for arm processors. This addresses a "bus error" test failure on some armhf systems. Not done for macOS. Fix L7 fuzz tests for armhf, plus add some more overflow protection.
This is what blocks tcpreplay to migrate to Debian testing, see https://bugs.debian.org/1009199
At first, sorry for not bringing this here earlier. I recall I already had analyzed the situation but as there is no bug report here, I must assume I never sent it, too bad.
So, this is the story: On armhf (but not armel), the tcpreplay test suite fails with various bus errors, for example:
Bisecting led to
... but I reckon simply reverting that one is not a sane way to deal with it. Perhaps in Debian, but certainly not upstream-wise. So I'm asking you to find a generic solution for this, for example by enhancing the check in autoconf so it will never trigger on MacOS?
The text was updated successfully, but these errors were encountered: