--- In
hercules-390@..., Ivan Warren <ivan@...> wrote:
>
> Paul,
>
> First, the correction to create_pipe/socketpair is correct (the 2nd &
> 3rd parameters are reversed).... But irrelevant to your problem !
Ok.
> In hercules, you have a good chance of this happening if the
> connect/accept sequence is taking an unusual amount of time
> to complete (a firewall may cause this for example).
Ok, perhaps combined with single-threading on my PC.
> Anyway.. Could you try this :
Thanks Warren. Unfortunately I'm still getting:
10:51:07 HHCSD004I Device 000C bound to socket localhost:3505
10:51:07 HHCSD020I Socketdevice listener thread started: tid=00001A04, pid=6684
10:51:07 ** Win32 porting error: invalid call to 'w32_select' from sockdev.c(43
10:51:07 HHCSD021E select failed; errno=0: No error
10:51:07 ** Win32 porting error: invalid call to 'w32_select' from sockdev.c(43
sockdev.c(437): mixed set(s)
(ie almost certainly -1)
on some runs, and:
HHCLG009S Syslog message pipe creation failed: The requested address is not vali
d in its context.
on other runs.
and working on 50% of runs.
I'll put back my debug info to see what's happening.
BFN. Paul.
