1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
RIOT/tests/cpp_ctors
2020-12-11 18:33:31 +01:00
..
tests tests: use check_unittests func from testrunner 2020-03-19 10:39:34 +01:00
main.c tests: remove uneeded DISABLE_MODULE+=auto_init 2020-02-12 16:51:34 +01:00
Makefile tests: remove uneeded DISABLE_MODULE+=auto_init 2020-02-12 16:51:34 +01:00
Makefile.ci tests: add samd10-xmini to Makefile.ci 2020-12-11 18:33:31 +01:00
README.md tests/cpp_ctors: move tests-cpp_ctors out of unittests 2019-08-22 12:39:47 +02:00
tests-cpp_ctors-class.cpp tests/cpp_ctors: move tests-cpp_ctors out of unittests 2019-08-22 12:39:47 +02:00
tests-cpp_ctors.cpp tests/cpp_ctors: move tests-cpp_ctors out of unittests 2019-08-22 12:39:47 +02:00
tests-cpp_ctors.h tests/cpp_ctors: move tests-cpp_ctors out of unittests 2019-08-22 12:39:47 +02:00

The purpose of this test is to ensure that C++ constructors are executed properly during the startup of RIOT. This requires that the port calls constructors somewhere during C-library initialization. On newlib ports this is done by __libc_init_array(), other ports may need to manually iterate through the list of initializer functions (usually .init_array), and call each one in order.

There are three tests:

  • Global constructor
  • Static constructor
  • Local constructor

The global constructor test checks to see if the constructor of a global object has been run during the boot process. The static constructor test does the same, but for static object inside a function. The local constructor test checks that a locally created object does have its constructor run. The local constructor test will only fail if there is a significant problem with the C++ tool chain, since it does not rely on any external C++ support code.