Re: mach_host_self() doesn't acquire new port name?!

[Roland McGrath]

> I don't understand why mach_host_self() doesn't acquire a new port name and
> leaks a port if not deallocated. In other words, I expected the following to
> leak ports, but it doesn't:
> 
> main ()
> {
>   while (1)
>     mach_host_self(); /* Returns 23 on each and every call. */
> }

I don't know why you would expect different from that call.  It is
returning a send right to the same port, so of course you get the same name
for adding more urefs to the same send right in the same task.