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

Testsuite fails on ppc64el #72

Closed
jcowgill opened this issue Jan 15, 2018 · 4 comments

Comments

@jcowgill
Copy link
Contributor

commented Jan 15, 2018

Running the testsuite on ppc64el fails with the following error (this is commit 93da162).

testing.capture-output ../../../bin.v2/libs/context/test/test_callcc_asm.test/gcc-7/release/link-static/threadapi-pthread/threading-multi/test_callcc_asm.run
====== BEGIN OUTPUT ======
Running 11 test cases...
unknown location(0): fatal error: in "Boost.Context: callcc test suite/_test_move": memory access violation at address: 0x00000000: no mapping at fault address
test_callcc.cpp(147): last checkpoint

*** 1 failure is detected in the test module "Master Test Suite"

EXIT STATUS: 201
====== END OUTPUT ======

Running fc fails with:

testing.capture-output ../../../bin.v2/libs/context/test/test_fcontext.test/gcc-7/release/link-static/threadapi-pthread/threading-multi/test_fcontext.run
====== BEGIN OUTPUT ======
Running 12 test cases...
f1: entered
unknown location(0): fatal error: in "Boost.Context: context test suite/_test_ontop": memory access violation at address: 0x3fffa94c4fb8: invalid permissions
test_fcontext.cpp(308): last checkpoint

*** 1 failure is detected in the test module "Master Test Suite"

EXIT STATUS: 201
====== END OUTPUT ======
@jcowgill

This comment has been minimized.

Copy link
Contributor Author

commented Jan 15, 2018

For good measure, running ec fails with:

testing.capture-output ../../../bin.v2/libs/context/test/test_execution_context.test/gcc-7/release/link-static/threadapi-pthread/threading-multi/test_execution_context.run
====== BEGIN OUTPUT ======                                                                                                                         
Running 13 test cases...                                                                                                                                                
unknown location(0): fatal error: in "Boost.Context: execution_context v2 test suite/_test_move": signal: SIGSEGV, si_code: 2137250680 (memory access violation at address: 0x00000003)
test_execution_context_v2.impl(236): last checkpoint                                                                                                                                                               
                                                                    
*** 1 failure is detected in the test module "Master Test Suite"
                                              
EXIT STATUS: 201                        
====== END OUTPUT ======

These are probably related to each other though.

@olk

This comment has been minimized.

Copy link
Member

commented Jan 16, 2018

are you sure? commit 93da162 only increases the stacksize from 64kB to 128kB
unfortunately I've no access to a PowerPC system - could you do a git bisect?

@jcowgill

This comment has been minimized.

Copy link
Contributor Author

commented Jan 17, 2018

ba357205a9968bc500563ade2fcdf23fb44c86a8 is the first bad commit
commit ba357205a9968bc500563ade2fcdf23fb44c86a8
Author: Oliver Kowalke <oliver.kowalke@gmx.de>
Date:   Fri Jan 1 22:03:18 2016 +0100

    class captured_context added

:040000 040000 b4bb4109325ab62d6883b7419696e448402f7cdc 7f59a322002f3ea4e1bbea173ea17ed4944b053f M      build
:040000 040000 275318b7f5bde9eb6dad96a8716eb60ddaa427b4 b676c7626d165737a255e4e2180f1bbb35702068 M      example
:040000 040000 4a8f5926ff811caff22f1b94e90689faedfe5b61 40bd1d1247ee099a55e631059e37b2a83ef613ab M      include
:040000 040000 256f828e46469c6f05ae8fe16e0b638ad46ec751 2edb64774e556889028b694761102ad345205170 M      performance
:040000 040000 41d05a56035bce91e32239cbf8e8a154c04777c7 38ecccbf5eedaf0a1df68692a3ad3361a4e6e7c9 M      src
:040000 040000 4365311c6f6f708e4b3b6884e11980a0ad5d1ab0 527284969b74954db9d38af9ef677539092ced4f M      test
@olk

This comment has been minimized.

Copy link
Member

commented Jan 17, 2018

ty, I'll take alook at it

@olk olk closed this in 2354eca May 4, 2019

olk added a commit that referenced this issue May 4, 2019
Merge pull request #106 from shawnanastasio/ppc64_elfv2_fix
Fix ABI violation on ppc64 ELFv2, fixes #72
owt5008137 added a commit to owt5008137/libcopp that referenced this issue Aug 20, 2019
Move changelog out of README.md.Merge boost.context 1.71.0
boost.context: https://www.boost.org/users/history/version_1_71_0.html
  Add support for RISC-V LP64D
  [#72](boostorg/context#72): Fix ABI violation on ppc64 ELFv2
  [#99](boostorg/context#99): cleanup of stack if creating ucontext fails
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.