Hello
> > > > However, since there seem to be a clean backtrace, maybe we could give a > > > > try anyway. Could you objdump your kernel image, then locate the faulty > > > > routine containing eip=0xc7b84d51? I can apply objdump to kernel modules, but when this utility was applied to kernel image, error message is displayed objdump: /boot/vmlinuz-xenomai: File format not recognized How could I objdump my kernel image? > > > Let's suppose we can believe in sanity of the call trace, then would > > > you, Victor, provide a disassembled code for > > > __ipipe_handle_exception() ? > > > I will do this with pleasure, one thing to know, which tools can help me? > > --- arch/i386/kernel/entry.S~ 2006-12-16 13:32:29.000000000 +0100 > > +++ arch/i386/kernel/entry.S 2007-01-26 23:44:59.000000000 +0100 > > @@ -1032,7 +1032,7 @@ > > RING0_INT_FRAME > > pushl $0 # no error code > > CFI_ADJUST_CFA_OFFSET 4 > > - pushl $do_divide_error > > + PUSH_XVEC(do_divide_error) > > s,PUSH_XVEC,PUSH_XCODE, > > > CFI_ADJUST_CFA_OFFSET 4 > > jmp error_code > > CFI_ENDPROC I did so. Thanks, Victor _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
