patrick keshishian wrote:
> On Tue, May 30, 2017 at 03:48:06AM -0400, Ted Unangst wrote:
> > + write(2, GREATSCOTT, sizeof(GREATSCOTT));
>^^
> maybe sizeof(GREATSCOTT)-1
indeed. (and typo fixed, thanks all)
On Tue, May 30, 2017 at 03:48:06AM -0400, Ted Unangst wrote:
> talking to stsp, he reminded me of a problematic bug that took some time to
> track down in some desktop software that shall not be named. after a program
> calls fork(), the child has only a single thread. per the standard, it needs
>
Il 30 mag 2017 09:48, "Ted Unangst" ha scritto:
talking to stsp, he reminded me of a problematic bug that took some time to
track down in some desktop software that shall not be named. after a program
calls fork(), the child has only a single thread. per the standard, it needs
to get to exec() as
talking to stsp, he reminded me of a problematic bug that took some time to
track down in some desktop software that shall not be named. after a program
calls fork(), the child has only a single thread. per the standard, it needs
to get to exec() as quickly as possible. per the quality standards of
