> > You're right, 0x4000673c does look like a shared library address, and is > not particularly illuminating unless you have access to the binary for > the library in question (which, obviously, I don't in this case). > > However, the next line of your crash dump contains the opcode sequence > around that address: > > Code: 1a000002 e594e060 e35e0000 1a0001d0 (ed5b0b23) > > The instruction in brackets is the actual one at which the fault > occurred. So, armed with that opcode 0xed5b0b23, you can then just feed > it into the disassembler and see what happens. > > The GNU tools don't actually have a direct equivalent to the ADS > "disass" program, so the easiest way to convert the opcode into an > instruction is along the lines of: > > $ arm-linux-as > .word 0xed5b0b23 > ^D > $ arm-linux-objdump -d a.out > >
Great. got it ! Thanks Khem and Phil for your great support. --RK _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
