DICE_NO_REPLY error

Michael Scheibel m.scheibel at sirrix.com
Fri Jul 21 17:20:36 CEST 2006


Hello list,

we have compiled the following interface with DICE 2.2.9:

UInt32 genBuf(
[out, size_is(*bufLen), max_is(MAX_BUFFER_SIZE)] UInt8** buf, 
[out] UInt32* bufLen,
[out, size_is(*buf2Len),  max_is(MAX_BUFFER_SIZE)] UInt8** buf2,  
[out] UInt32* buf2Len);

UInt32 is defined as unsigned long, UInt8 as unsigned char, and 
MAX_BUFFER_SIZE is 4096.

DICE options are
-ftrace-server=printf
-ftrace-client=printf
-fforce-corba-alloc
-P-DRAM_BASE=0x0 
-P-DUSE_DIETLIBC=y
-P-DSYSTEM_x86_l4v2
-P-DARCH_x86 
-P-DCPUTYPE_ 
-P-DL4API_l4v2
-template
-Bpia32 
-Biv2 
-BmC

Running the generated stubs we noticed that ~0.89% of the IPC transactions 
fail. In such a case the parameters passed to the server still contain their 
initialization values on return. The client trace says "ipc error c0" and the 
server trace says "DICE_NO_REPLY".

We would be happy about some hints what's going wrong here...

Michael

-- 
Sirrix AG security technologies - http://www.sirrix.com
Michael Scheibel  eMail: m.scheibel at sirrix.com
Tel +49(234) 610 071-124
Public key on demand.
Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54

This message may contain confidential and/or privileged information. 
If you are not the addressee, you must not use, copy, disclose or 
take any action based on this message or any information herein. 
If you have received this message in error, please advise the sender 
immediately by reply e-mail and delete this message.  




More information about the l4-hackers mailing list