-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
>>> And at 15c7a8 there is e12fff37 <=> blx r7 , which i've >>> already found in MOE. But that's not what i'm looking for, is >>> it? >> >> This has nothing to do with MOE. When you objdump the myClient >> binary, can you find the address in there? Does the binary >> contain blx r7 as well? > > No, this instruction or PC is not in myClient nor in myServer. But > i can find the instruction in a shared lib which myServer uses. No. We are definitely looking at myClient as this is where the page fault happens. Please objdump myClient and find the page fault PC again. >>> Goto f118a000, gives me the PC=15c7a8 again, where the Error >>> happens. >> >> Yep, the UTCB contains the exception message informing the >> exception handler about the page fault. This is the effect of >> your page fault, not the cause. > > Well then, where do i find the cause for the page error? Do i need > a deeper unterstanding of the stack, or shall i just look at the > instructions around PC=15c7a8 ? Actually I still think we are looking for the instruction exactly at this location. How does the objdump around this area look like? Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRwVFQACgkQP5ijxgQLUNmDIACeL3nIJPZwZg0d4Dg3KvWS9+If 3HEAoJO6VELf21MImLsm9SuF4sBkNhUQ =2Ss9 -----END PGP SIGNATURE----- _______________________________________________ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
