Hi,
attached there is a patch for the Hurd recvfrom(). It avoids the
application to get a SIGLOST as a indirect consequence of a null mach
port being used.
Thanks,
--
Pino Toscano
hurd: recvfrom(): take into account null address ports
Some kinds of sockets may return a null address port when
Pino Toscano, le Wed 23 Nov 2011 16:42:41 +0100, a écrit :
> On Linux the address length is set to 0 by recvfrom(), so I guess that
> this kind of sockets have no address?
I'd say so, yes, and so recvfrom should gracefully set an empty address.
Samuel
Hallo!
On Sat, 26 Nov 2011 15:53:45 +0100, Christian Grothoff
wrote:
> Thank you Thomas for your suggestion. For our purposes, this is a
> better (certainly more portable) solution that does always work.
Great that Thomas Bushnell could help finding a yet-better solution for
the original prob
Thank you Thomas for your suggestion. For our purposes, this is a
better (certainly more portable) solution that does always work.
Happy hacking,
Christian
On 11/26/2011 02:43 AM, Thomas Bushnell, BSG wrote:
Oh, and in the case you describe there:
The hypervisor at start creates a global va
Samuel Thibault, le Sat 26 Nov 2011 15:14:11 +0100, a écrit :
> Richard Braun, le Sat 26 Nov 2011 15:12:50 +0100, a écrit :
> > On Sat, Nov 26, 2011 at 11:35:29AM +0100, Samuel Thibault wrote:
> > > > (Naturally, the result would be non-portable for systems where
> > > > fork==vfork,
> > > > but t
Richard Braun, le Sat 26 Nov 2011 15:12:50 +0100, a écrit :
> On Sat, Nov 26, 2011 at 11:35:29AM +0100, Samuel Thibault wrote:
> > > (Naturally, the result would be non-portable for systems where
> > > fork==vfork,
> > > but then maybe implementing vfork as fork is the bug? ;-))
> >
> > It's what
On Sat, Nov 26, 2011 at 11:35:29AM +0100, Samuel Thibault wrote:
> > (Naturally, the result would be non-portable for systems where fork==vfork,
> > but then maybe implementing vfork as fork is the bug? ;-))
>
> It's what the norm says.
I think you meant the norm explicitely says vfork can be imp
Christian Grothoff, le Sat 26 Nov 2011 01:09:59 +0100, a écrit :
> On 11/25/2011 07:50 PM, Thomas Bushnell, BSG wrote:
> >Programs which depend on the special suspend-the-parent behavior of
> >vfork were always regarded as buggy...
>
> So relying on the well-documented behavior of a system call is
