On Tue, 2006-09-26 at 21:34 +0200, Niklaus Giger wrote: > Here is the stack with adeos-ipipe 1.3 after applying your patch > > (gdb) info stack > #0 xnpod_fault_handler (fltinfo=0xc1489e18) at > kernel/xenomai/nucleus/pod.c:216 > #1 0xc004bad4 in xnpod_trap_fault (fltinfo=0x73) at > kernel/xenomai/nucleus/pod.c:2907 > #2 0xc0043ee8 in xnarch_trap_fault (event=115, domid=0, data=0xc01a9435) at > include/asm/xenomai/bits/init.h:46 > #3 0xc012dc38 in exception_event (event=3223286668, ipd=0x0, > data=0xc01a9435) > at arch/ppc/xenomai/hal.c:385 > #4 0xc003fe18 in __ipipe_dispatch_event (event=0, data=0xc1489f50) at > kernel/ipipe/core.c:665 > #5 0xc000aecc in do_page_fault (regs=0xc1489f50, address=268448708, > error_code=0) at include/linux/ipipe.h:445 > #6 0xc0003258 in handle_page_fault ()
The function parameters look weird, but the backtrace seems ok. This tells us that it's not related to FPU emulation, but rather to an invalid memory access. > Previous frame inner to this frame (corrupt stack?) > (gdb) > > Hope it helps you -- Philippe. _______________________________________________ Xenomai-core mailing list [email protected] https://mail.gna.org/listinfo/xenomai-core
