<adamrbk>
this is running on 32-bit linux so maybe that's the issue?
<hannes>
adamrbk: this is interesting, the 32bit runtime might be an issue -- there is an open issue at mirage-clock https://github.com/mirage/mirage-clock/issues/17 talking about 32bit thingies... you can also try to send a mail to mirageos-devel, there are more listeners than here
<adamrbk>
thanks hannes
<adamrbk>
That looks like it might be the same issue - my stack trace did have the exception raised in mirage-logs
<hannes>
adamrbk: if you feel comfortable, the issue suggests to adapt some C code in mirage-clock, might be worth to give it a shot, and submit a PR/ask on the issue..
<adamrbk>
yeah I'll look into it
yomimono has quit [Ping timeout: 260 seconds]
yomimono has joined #mirage
insitu has joined #mirage
insitu has quit [Client Quit]
yomimono has quit [Ping timeout: 252 seconds]
yomimono has joined #mirage
AltGr has left #mirage [#mirage]
cbarrett has quit []
cbarrett has joined #mirage
tomboy64 has quit [Ping timeout: 248 seconds]
tomboy64 has joined #mirage
copy` has joined #mirage
adamrbk has quit [Ping timeout: 240 seconds]
tomboy64 has quit [Remote host closed the connection]
tomboy64 has joined #mirage
adamrbk has joined #mirage
insitu has joined #mirage
yomimono has quit [Ping timeout: 240 seconds]
adamrbk has quit [Ping timeout: 252 seconds]
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]