Hi Aditya,
On 07/23/2014 01:27 PM, Aditya Kousik wrote:
Hello Stefan,
Three months ago, when I received a page fault (RM error), Norman suggested using objdump and I did it as follows with Genode toolchain: In var/run/printf: $ /usr/local/genode-gcc/arm-elf-eabi/bin/objdump -lSd image.elf | less
The problem is that you used the stripped (all debugging symbols deleted) overall image with objdump, thereby you don't gain any line information resp. correlation to the higher level language. Try the following instead:
/usr/local/genode-gcc/arm-elf-eabi/bin/objdump -lSd bin/core | less
If you've "c++filt" installed, you might imply it into your pipe chain to demangle C++ symbols:
/usr/local/genode-gcc/arm-elf-eabi/bin/objdump -lSd bin/core | c++filt | less
Regards Stefan
While we were able to find the conflicting address and IP, it was of no help because we couldn't trace it to the faulty line (primarily because we don't speak hexa). Is there a way of doing this, that is, Finding which line of code the IP is a part of?
Thanks Aditya.
Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main