zephyr/tests/lib/mem_alloc/prj_newlib.conf

CONFIG_ZTEST=y
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_NANO=n
CONFIG_NEWLIB_LIBC_ALIGNED_HEAP_SIZE=512
CONFIG_TEST_USERSPACE=y
tests: lib: mem_alloc: Add tests to validate dynamic allocation Add new test cases to validate dynamic memory allocation functions such as malloc, calloc, realloc using minimal libc and newlibc implementation of standard C library. Signed-off-by: Praful Swarnakar <praful.swarnakar@intel.com> 2018-08-02 11:06:59 +08:00			`CONFIG_ZTEST=y`
			`CONFIG_NEWLIB_LIBC=y`
tests: lib: mem_alloc: Fix incorrect newlib variant usage NEWLIB_LIBC_NANO defaults to y when building with a toolchain that supports nano.specs and this was causing the libraries.libc.newlib test to link with the newlib nano variant (libc_nano.a) when it should be linking with the normal newlib (libc.a). By setting CONFIG_NEWLIB_LIBC_NANO=n in prj_newlib.conf, we make sure that the libraries.libc.newlib test links with the normal newlib. For more details, refer to the issue #21167. Signed-off-by: Stephanos Ioannidis <root@stephanos.io> 2019-12-04 16:28:59 +08:00			`CONFIG_NEWLIB_LIBC_NANO=n`
libc: set up memory partitions * Newlib now defines a special z_newlib_partition containing all globals relevant to newlib. Most of these are in libc.a with a heap tracking variable in newlib's hooks. * Both C libraries now expose a k_mem_partition containing the bounds of the malloc heap arena. Threads that want to use libc malloc() will need to add this to their memory domain. * z_newlib_get_heap_bounds has been removed, in favor of the memory partition for the heap arena * ztest now includes the C library partitions in its memory domain. * The mem_alloc test now runs in user mode to prove that this all works for both C libraries. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2019-02-02 04:18:31 +08:00			`CONFIG_NEWLIB_LIBC_ALIGNED_HEAP_SIZE=512`
tests: CONFIG_TEST_USERSPACE now off by default Unlike CONFIG_HW_STACK_PROTECTION, which greatly helps expose stack overflows in test code, activating userspace without putting threads in user mode is of very limited value. Now CONFIG_TEST_USERSPACE is off by default. Any test which puts threads in user mode will need to set CONFIG_TEST_USERSPACE. This should greatly increase sanitycheck build times as there is non-trivial build time overhead to enabling this feature. This also allows some tests which failed the build on RAM-constrained platforms to compile properly. tests/drivers/build_all is a special case; it doesn't put threads in user mode, but we want to ensure all the syscall handlers compile properly. Fixes: #15103 (and probably others) Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2019-04-06 06:39:50 +08:00			`CONFIG_TEST_USERSPACE=y`