[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mach_host_self() doesn't acquire new port name?!
From: |
Roland McGrath |
Subject: |
Re: mach_host_self() doesn't acquire new port name?! |
Date: |
Sun, 6 May 2001 16:46:45 -0400 (EDT) |
> 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.
- mach_host_self() doesn't acquire new port name?!, Marcus Brinkmann, 2001/05/06
- Re: mach_host_self() doesn't acquire new port name?!,
Roland McGrath <=
- Re: mach_host_self() doesn't acquire new port name?!, Marcus Brinkmann, 2001/05/06
- Re: mach_host_self() doesn't acquire new port name?!, Roland McGrath, 2001/05/06
- Re: mach_host_self() doesn't acquire new port name?!, Marcus Brinkmann, 2001/05/06
- Re: mach_host_self() doesn't acquire new port name?!, Roland McGrath, 2001/05/06
- Re: mach_host_self() doesn't acquire new port name?!, Marcus Brinkmann, 2001/05/07
- Re: mach_host_self() doesn't acquire new port name?!, Thomas Bushnell, BSG, 2001/05/07
- Re: mach_host_self() doesn't acquire new port name?!, Thomas Bushnell, BSG, 2001/05/07
- Re: mach_host_self() doesn't acquire new port name?!, Marcus Brinkmann, 2001/05/08
- Re: mach_host_self() doesn't acquire new port name?!, Thomas Bushnell, BSG, 2001/05/08
- Re: mach_host_self() doesn't acquire new port name?!, Marcus Brinkmann, 2001/05/08