RE: Pagefault in StringItem IPC

Could it be that the string you're trying to send is not mapped? That the UIP is at the ipc entry doesn't mean that the pagefault has occurred there. FYI, L4 has two tracing tools that to print out what's going on in the kernel and which kernel events and operations have been invoked. They're called tracebuffer (kdb menu 'y'),  which is a log of kernel events and tracepoints (kdb menu 'r'); you have to enable them in the config menu. 

-Jan

--
Dr.-Ing. Jan Stoess
KIT/UKa System Architecture Group
Phone: +49 (721) 608 4056
Fax: +49 (721) 608 7664
http://os.ibds.kit.edu/stoess 


> -----Original Message-----
> From: [email protected] [mailto:[email protected]
> karlsruhe.de] On Behalf Of BERTRAND Joel
> Sent: Tuesday, November 30, 2010 19:43
> To: [email protected]
> Subject: Re: Pagefault in StringItem IPC
> 
> Some news. When I try to execute step after step my program, it hangs on
> line :
> 
>    200321:   ff 14 25 40 1b 20 00    callq  *0x201b40
> 
> cauchy:[~/openvms/mnt/boot] > nm pager.sys | grep 201b40
> 0000000000201b40 B __L4_Ipc
> 
> 	If I understand, my function tries to jump to address 0x201b40
> (L4_Call() entry point) that is not accessible. Why ?
> 
> 	JB