Brian Callahan <[email protected]> writes:

> Hi Omar --
>
> On 1/25/2022 5:36 AM, Omar Polo wrote:
>> Hello,
>> 
>> algol68g saw some further developments recently with a major version
>> released some time ago.  Among various things, it also includes the fix
>> for the usleep issue we found :)
>> 
>
> I took at quick look at this. It looks like upstream still gets the
> check wrong though. IIRC, it checks to see if the return value for
> usleep is EINTR instead of the return value being -1 and errno being set
> to EINTR.

Yes...  I just grepped for usleep and stopped when seeing the ASSERT.
it needs to the same fix for the previous version.  (which is strange
since upstream merged the correct fix a couple of months ago.)

> [...]
>
> I had a half-finished diff that was a little different than yours. I'll
> triangulate and see if I can't figure out this shared object issue in
> the test over the new few days.

thanks!

Reply via email to