[bug #49278] fprintf(stderr, ...) returns -1 (EINTR)

Follow-up Comment #1, bug #49278 (project hurd): I suspect this is caused by a no-more-senders notification on the receive right of the filesystem root port, to which the client sent the message. If you add sleep(2) after the mach_msg call in the client, so that it doesn't deallocate the send rig

[bug #49278] fprintf(stderr, ...) returns -1 (EINTR)

URL: Summary: fprintf(stderr, ...) returns -1 (EINTR) Project: The GNU Hurd Submitted by: baccala Submitted on: Thu 06 Oct 2016 04:44:51 AM GMT Category: Hurd Severity:

[bug #48930] crash server crashes after --core-file-name is changed with fsysopts

Follow-up Comment #4, bug #48930 (project hurd): The fix looks OK, except I don't like the assumption that argp_error will preserve errno. It will hold in practice though, unless someone specifies ARGP_NO_EXIT without ARGP_NO_ERRS. Currently only console-client/ does that. _

Re: fprintf failing with EINTR

Hello, Brent W. Baccala, on Tue 04 Oct 2016 15:26:51 -1000, wrote: > I've seen this behavior several times with Hurd: fprintf(stderr, ...) will > return -1 with errno = EINTR. > I have a test program that reproduces it consistently.  Should I file it as a > bug report? Yes, please. We used to h

[bug #48930] crash server crashes after --core-file-name is changed with fsysopts

Update of bug #48930 (project hurd): Open/Closed:Open => Closed ___ Reply to this item at: ___ Messag

[bug #48930] crash server crashes after --core-file-name is changed with fsysopts

Update of bug #48930 (project hurd): Status:None => Fixed ___ Follow-up Comment #3: Fixed as of 74998f9d. ___ Reply to this i