Niklaus Giger wrote:
> Hi
>
> I compiled and started my test with a recent xenomai/trunk (revision 1068).
> I booted into single user mode, did a "modprobe xeno_vxworks" (no problem)
> and
> then a "rmmod xeno_vxworks" and got as response on my PowerBook only
> "Kernel panic: -not syncing: Aiee, killing interrupt handler".
>
>
> Also when I try to run ksrc/skins/vxworks/demos/satch (after a make std)
> I get the following info (using gdb):
> (gdb) run
> Starting
> program: /mnt/data.ng/hcu/kernel/xenomai-head/ksrc/skins/vxworks/demos/satch
> [Thread debugging using libthread_db enabled]
> [New Thread 805415264 (LWP 4168)]
> [New Thread 805434592 (LWP 4171)]
> [New Thread 805450976 (LWP 4172)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 805434592 (LWP 4171)]
> 0x0fe76094 in vfprintf () from /lib/tls/libc.so.6
> (gdb) info stack
> #0 0x0fe76094 in vfprintf () from /lib/tls/libc.so.6
> #1 0x0fe7e760 in printf () from /lib/tls/libc.so.6
> #2 0x10001a6c in consumer_task (a0=269287424, a1=268894208, a2=269477288,
> a3=0, a4=0, a5=0, a6=269482760, a7=805474048,
> a8=2144297840, a9=268064096) at satch.c:99
> #3 0x0ffa7714 in wind_task_trampoline (cookie=0x7fcf632c)
> at /mnt/data.ng/hcu/kernel/xenomai-head/src/skins/vxworks/taskLib.c:99
> #4 0x0ffd08e8 in start_thread () from /lib/tls/libpthread.so.0
> #5 0x0ffd08e8 in start_thread () from /lib/tls/libpthread.so.0
> Previous frame inner to this frame (corrupt stack?)
I observed such an error when the stack size is to small, I guess
vfprintf uses alloca.
--
Gilles Chanteperdrix.
_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
