Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cunixf.cc.columbia.edu!cs.columbia.edu!mail
From: bill@cs.columbia.edu (Bill Schilit)
Newsgroups: comp.os.mach
Subject: MIG+netmsgserver bug?
Message-ID: <9011110250.AA29362@cs.columbia.edu>
Date: 11 Nov 90 02:50:56 GMT
Lines: 27

Hi,

I am getting messages rejected from a MIG generated xxx_server() with
return code MIG_BAD_ARGUMENTS.  The cause appears to be differences in
the msg_type_t fields of the incoming message and the msg_type_t field
of the MIG generated static Check structure.  The differing field is
msg_type_deallocate which the static Check structure wants to be TRUE
but the message says is FALSE.  The client side *is* setting the bit
to TRUE.

I can run the interface locally on one machine and it works fine, but
between two hosts it breaks.  I found a suspicious comment in
netmsgserver (ipc_in.c) that says:

	 *  2-Jan-87  Robert Sansom (rds) at Carnegie Mellon University
	 *	Minor changes to integrate with other modules.
	 *	Always set deallocate bit to FALSE.


There are two types of checks in mig generated code, so I will try
setting -DUseStaticMsgType=0 which uses a field by field comparison of
msg_type_t and skips the msg_type_deallocate field (!).

However I'm still wondering what the story is and if anyone else has
seen this problem...

- Bill