76fc34baeb
The C++/UNO bridge for macOS on arm64 currently uses the Linux code. Apple's ABI uses slightly different parameter passing on the stack, though. See https://developer.apple.com/documentation/xcode/writing_arm64_code_for_apple_platforms?language=objc That has not been taken into account yet in the bridge code. The bridgetest, when run on macOS on arm64, didn't notice, sadly, but succeeded. With this change it crashes, as one would expect it to do. Add one more byte and short parameter to the setValues(), setValues2() and getValues() calls in the XBridgeTestBase interface. The stack allocation for those [in] parameters to setValues() differ between the Linux and Apple ABIs. Add corresponding attributes to the interface, and members to the SimpleTest struct. The changes to the source files in the cli subdirectory (C++/CLI, VB.NET, and C#) are done blindly as they aren't compiled even on Windows currently. Most likely the changes to them are incomplete and erroneous. Change-Id: I6f689a130d89b23cad9918829107d7da49a79c55 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105770 Tested-by: Tor Lillqvist <tml@collabora.com> Reviewed-by: Tor Lillqvist <tml@collabora.com> |
||
|---|---|---|
| .. | ||
| com/sun/star/comp/bridge | ||
| qa | ||
| source | ||
| CustomTarget_bridgetest.mk | ||
| CustomTarget_bridgetest_climaker.mk | ||
| CustomTarget_bridgetest_javamaker.mk | ||
| CustomTarget_uno_test.mk | ||
| InternalUnoApi_bridgetest.mk | ||
| InternalUnoApi_performance.mk | ||
| Jar_testComponent.mk | ||
| Library_bridgetest-common.mk | ||
| Library_bridgetest.mk | ||
| Library_constructors.mk | ||
| Library_cppobj.mk | ||
| Makefile | ||
| Module_testtools.mk | ||
| Rdb_uno_services.mk | ||
| README | ||
Testing tools == How to check compatibility between compilers == Since the interfaces used in the cpp bridgetest are not changed often one can just build the cppobj.uno.dll and the constructors.uno.dll (testtools/source/bridgetest) in an old environment and then use them in the new environment. That is the files are copied into the testtools/wntmsciXX.pro folder which corresponds to the new environment. On Windows this test will typically fail because the tests use the cppu::getCaughtException function, which only works when all libs are build using the same runtime. This part of the test can switched off. To do this go into the testtools/source/bridgetest folder and call dmake compcheck=1 This will add a new compiler define (-DCOMPCHECK) and will be used in the bridgetest.cxx to switch off the code which uses the getCaughtException function. However, there is still a test which causes the test component to throw and IllegalArgumentException. This still works. == Using source/bridgetest for stress testing == Start a modified bridgetest_server (with the final "--singleaccept" argument removed from the uno executable call) or a modified bridgetest_javaserver (with the final "singleaccept" argument replaced with "multi" in the java executable call), then start a modified bridgetest_client (with a final "stress" argument added to the uno executable call). The client will continuously establish connections to the server which are immediately destroyed again. The test will run forever, unless an error occurs.