Hello Leslie,

On 02/06/17 05:52, Leslie Zhai wrote:

Thanks for your reply! but I met the same story for L4Linux https://pbs.twimg.com/media/DBSQtoNUIAEE2HY.png

It looks like the very same error, an unhandled read page-fault at address 0x18 triggered by an instruction at 0x102d72a.

> Maybe you could use addr2line/objdump
> to figure out, what happens at address 0x102d72a in ned.

cd /home/zhaixiang/project/l4re/l4/build
addr2line -p -e bin/amd64_K8/l4f/ned 0x102d72a

but there is no output easy to read for humans, I am not familiar with addr2line, please give me some advice, thanks a lot!

If I try it with an instruction pointer somewhere in the main function it looks like follows:

~/build/tmp/l4re/bin/amd64_K8/l4f$ addr2line -p -i -e ned -a 10038b3
0x00000000010038b3: /home/.../src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:39
 (inlined by) /home/.../src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:75

objdump -D bin/amd64_K8/l4f/ned > ned.S

If you use -lSd you should see line number information in the disassembled output, e.g:

/home/.../src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:39
  for (int i = 0; i < argc; ++i)
 10038b3:       85 db                   test   %ebx,%ebx

 

102d72a:   66 0f 12 05 9e 7b 02    movlpd 0x27b9e(%rip),%xmm0 # 10552d0 <_ZL7HOOKKEY+0x        8>
is it enough to figure out what happened? if not, I will upload the disassemble to my Google drive.

This looks strange. There is nothing looking like an access to 0x18. Could send me your ned binary?

regards,
Jean

-- 
Regards,
Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/