On 12/03/15 18:41, Joel Sherrill wrote:
Hi Many BSPs can link a test but don't actually have enough memory to run the test. They will fail in the first few lines when the requested memory for the RTEMS work area is not available. I hacked together a script which adds together the code, data, bss, work space and stack space requested. If this exceeds physical memory on the board, then the test will fail. It is possible to come close and still run out of memory during initialization (e.g. malloc, etc) but this approach could detect some tests which will fail by inspecting them on the host. This is a shell script but would be better built into the rtems-tools and using the gdb/mi. Combined with information on the available memory on the target, we could throw out some obvious failure cases without touching hardware. Thoughts?
I would address this with better test output, so that you can get a summery and see "X tests failed due to not enough memory for the workspace".
-- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
