Segfault on second `getMessage()` call after EAGAIN error about nim-chronos HOT 5 CLOSED

I need to understand when EAGAIN happens, at the end or in process?

from nim-chronos.

in process, the err var here contains it:

And then it gets raised by the getMessage call in the handler. The segfault happens only later on a second getMessage.

from nim-chronos.

But why you are trying to perform one more getMessage()?

from nim-chronos.

I don't. It gets called automatically by the handler on next data received by same DatagramTransport.

from nim-chronos.

I think I found the root cause of my EAGAIN error. It is due to a poll() in an async proc (which is not nice anyhow, but that was not the point).
If you look at the poll() code it makes sense that this can happen, although it requires some conditions.

A "normal" poll() which adds the async proc with the poll() inside to the callbacks and next also the readDatagramLoop handler on an Event.Read . processCallbacks must run first the async proc with poll(). Next in that poll again Event.Read for same socket, processCallbacks runs again, both callbacks are run ... et voila, EAGAIN

So I guess this can be closed, but perhaps some documentation could be added that this should not be done.

from nim-chronos.