Hello Genode, When running the test program on Fiasco.OC, often a page fault occurs.
I assume that, I made a bug by misusing of a shared library. However, I don't know how to get a shared library text.
for example, /proc/id/maps on linux: ( or pmap ) root:/proc/1# cat maps b74fa000-b7505000 r-xp 00000000 08:01 10384183 /lib/i386-linux-gnu/ libnss_files-2.15.so b7505000-b7506000 r--p 0000a000 08:01 10384183 /lib/i386-linux-gnu/ libnss_files-2.15.so ...
I want to get a section information of shared library for finding a cause of page fault.
What should I do for solving this question?
Hello Younwoo Kim,
On 01/14/2013 07:53 AM, Younwoo Kim wrote:
Hello Genode, When running the test program on Fiasco.OC, often a page fault occurs.
I assume that, I made a bug by misusing of a shared library. However, I don't know how to get a shared library text.
for example, /proc/id/maps on linux: ( or pmap ) root:/proc/1# cat maps b74fa000-b7505000 r-xp 00000000 08:01 10384183 /lib/i386-linux-gnu/ libnss_files-2.15.so b7505000-b7506000 r--p 0000a000 08:01 10384183 /lib/i386-linux-gnu/ libnss_files-2.15.so ...
I want to get a section information of shared library for finding a cause of page fault.
What should I do for solving this question?
you can apply the following patch: https://raw.github.com/cproc/genode_stuff/tmp/tmp/ldso_show_link_addr.diff
Then the dynamic linker will show the shared library address ranges as debug output.
Regards, Christian