poll() with POLLIN not set still getting hit

RE: poll() with POLLIN not set still getting hit

Hakon — Thu, 14 May 2020 08:18:48 GMT

I tried with the serial modem sample and ran the same at command sequence as you, and the modem seemed to be unresponsive after. I also found out that this could be related to a bug that has already been reported.

RE: poll() with POLLIN not set still getting hit

erik.johnson — Tue, 12 May 2020 19:49:49 GMT

*sigh* It looks like it's probably because of a dumb mistake I made in my code. I think can probably be closed (which I'll do when I confirm this is the case).

RE: poll() with POLLIN not set still getting hit

erik.johnson — Tue, 12 May 2020 14:31:45 GMT

Our code isn't really in a form where I can give you a simple snippet to run on your own, but I guess I could try putting together an example. It should be pretty straightforward to do yourself, though.

RE: poll() with POLLIN not set still getting hit

Hakon — Tue, 12 May 2020 13:42:28 GMT

Hello,

do you have any code so I can reproduce the issue? It could be a bug.

RE: poll() with POLLIN not set still getting hit

erik.johnson — Thu, 07 May 2020 20:29:06 GMT

Actually, I take part of that back: the POLLIN bit appears to remain active even after reading in all of the data (allowed 576 bytes, read 368). It looks like revents isn't cleared by the poll() call, which is why it looked like the bit was continuing to be set. When I manually clear it between each poll() call, the bit doesn't show up the next time poll() exits, but poll() does still exit each time, which to me implies *something* is getting permanently stuck somewhere.

RE: poll() with POLLIN not set still getting hit

erik.johnson — Thu, 07 May 2020 18:27:29 GMT

Sorry, didn't include that we're using version 1.1.1 of the firmware.