Hello > Let's suppose we can believe in sanity of the call trace, then would > you, Victor, provide a disassembled code for > __ipipe_handle_exception() ? > > Call Trace: > [<c0112566>] __ipipe_handle_exception+0x58/0x11e > [<c01050f4>] do_divide_error+0x0/0xb1 > [<c0309202>] error_code+0x3e/0x4c > > > Memory: 384496k/393152k available (2088k kernel code, 8108k reserved, > 633k data, 180k init, 0k highmem) > virtual kernel memory layout: > fixmap : 0xfffb7000 - 0xfffff000 ( 288 kB) > vmalloc : 0xd8800000 - 0xfffb5000 ( 631 MB) > lowmem : 0xc0000000 - 0xd7ff0000 ( 383 MB) > .init : 0xc03ac000 - 0xc03d9000 ( 180 kB) > .data : 0xc030a212 - 0xc03a88f4 ( 633 kB) > .text : 0xc0100000 - 0xc030a212 (2088 kB)
Attached file contains objdump -D of my kernel image with __ipipe_handle_exception function. How could I locate the faulty routine containing eip=0xc7b84d51? Thanks, Victor
disassembled.bz2
Description: application/bzip
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
