Re: [PATCH 8/8] rpctrace: use condition variable to keep messages in sequence

Hello, Better apply this patch before patch7, shouldn't we? Otherwise there's a little git interval during which rpctrace is unreliable. Samuel

Re: [PATCH 1/8] remove warning messages on rpctrace from 'asprintf'

Hello, > #define easprintf(args...)assert(asprintf (args) != -1) That will be removed when building with -DNDEBUG, not a good thing :) Also, I don't see copyright assignment in the FSF records, did you start making one? Samuel

Re: [PATCH 8/8] rpctrace: use condition variable to keep messages in sequence

Brent W. Baccala, on Sat 29 Oct 2016 13:48:23 -1000, wrote: > I had thought of the entire patch set being applied monolithically. Yes, but that'll still appear as separate commits, that some people might fall in the middle of while bisecting something. > Yes, patch7 without patch8 can reorder

Re: [PATCH 8/8] rpctrace: use condition variable to keep messages in sequence

On Oct 29, 2016 2:55 AM, "Samuel Thibault" wrote: > > Hello, > > Better apply this patch before patch7, shouldn't we? Otherwise there's > a little git interval during which rpctrace is unreliable. > > Samuel I had thought of the entire patch set being applied

Re: [PATCH 1/8] remove warning messages on rpctrace from 'asprintf'

On Oct 29, 2016 2:53 AM, "Samuel Thibault" wrote: > > Hello, > > > #define easprintf(args...)assert(asprintf (args) != -1) > > That will be removed when building with -DNDEBUG, not a good thing :) An excellent point. I'll revise PATCH 1 tomorrow. > Also, I

Re: Mach "pipe" between parent and child

Hi, On Tue, Oct 25, 2016 at 05:59:34PM -1000, Brent W. Baccala wrote: > What is the best way to fork() a child and have a Mach receive right on the > parent connected to a send right on the child? I wonder whether it's possibly to just wrap the send right in a fake file descriptor, so fork()

Re: Mach "pipe" between parent and child

Olaf Buddenhagen writes: > I wonder whether it's possibly to just wrap the send right in a fake > file descriptor, so fork() clones it automatically?... No, file descriptors do not affect what fork does to Mach ports. * If the parent task has a receive right, then fork