Hi Theo, On Wed, Mar 25, 2009 at 12:38 AM, Theo Markettos <[email protected]> wrote:
> First I thought it was the callback veneers, but replacing with those in the > EtherY module (from which EtherRPCEm is derived, and runs OK on > RPCEmu/RO4.39 even if there's no Castle Ethernet hardware) shows it doesn't > make any difference. Then I thought there was something up with the service > call handler, but service calls seem to be despatching OK. AFAIK it's > something happening /after/ a service call is received, but given the DCI4 > startup process is replete with service calls this doesn't help that much. > What I don't understand is what's changed since 4.02 (and couldn't see > anything notable in the logs). I did some swi logging when the module hangs. The system comes in a loop and wants constantly lookup an error with MessageTrans_ErrorLookup. I trapped the error token and I got this message: HeapBadReason:Bad reason code. I hope this can help you in some way. MrSeed _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
