Niklaus Giger wrote:
> Running the sim testsuite vxworks (revision 1078) (using the attached
> I get the following a few failures and memory corruption:
> trestart.c:46, taskSpawn("nop", 19, 0, 32768, nopTask, 0,0,0,0,0,0,0,0,0,0)
> *** glibc detected *** malloc(): memory corruption: 0x100bf000 ***
> t010726-1.log:t010726-1.c:106, test finished: 4 failures/ 15 tests
> t010726-2.log:t010726-2.c:224, test finished: 0 failures/ 82 tests
> t010728.log:t010728.c:119, test finished: 0 failures/ 4 tests
> t010820-1.log:t010820-1.c:90, test finished: 0 failures/ 23 tests
> t010820-2.log:t010820-2.c:81, test finished: 0 failures/ 11 tests
> t010823-1.log:t010823-1.c:114, test finished: 0 failures/ 16 tests
> t010823-2.log:t010823-2.c:166, test finished: 1 failures/ 33 tests
> Is this normal or a powerpc specific error of the Xenomai simulator?
The tests run here without any failure, however the round-robin test
relies on a precise number of "virtual cycles" which is probably
In order to display the errors, you should grep '^[^ ]*:[0-9]*:' in the
> How do I debug trestart as it is not a fully linked executable?
trestart is a script, the fully linked executable is in the .libs
directory, because of libtool. There is a way to run gdb using the
script arguments, which I do not remember, something like
> Is it normal that a "make check" only works, if one builds the simulator
> inside the source code?
Last time I checked it worked when built out-of-tree, but you must build
the simulator in the sim subdirectory of a xenomai build directory.
Xenomai-core mailing list