Hi Fotis,
Yes, I understood the point. Because it needs the right timing it
could be trick to duplicate.
Did you try to create a simple host server to try to emulate this
connection issue?
BR,
Alan
On 8/12/22, Fotis Panagiotopoulos wrote:
> I think I understand the nature of the bug.
>
> When
Hi Fotis,
Nice, seems like you are narrowing down the numbers of variables, it
will make easier to let us to replicate the issue when you find it.
You also can use coloration and canaries to help with memory issues.
BR,
Alan
On 8/12/22, Fotis Panagiotopoulos wrote:
> Hi Alan,
>
> I am trying
I think I understand the nature of the bug.
When closing a socket, tcp_close_eventhandler() is set as a callback in the
dev->d_devcb list.
Typically, the server's response (FIN ACK) will have as a result
tcp_callback() to be executed, and thus the callback to be properly called,
with proper argum
Hi Alan,
I am trying hard to reproduce the issue reliably, but I haven't been able
to do so yet.
I noticed that when I disable CONFIG_NET_TCP_WRITE_BUFFERS, the problem
does not disappear, rather it changes form.
Now I occasionally get a failed assertion in wdog/wd_cancel.c line 95.
I have to me
Hi Alin,
I fixed it here: https://github.com/apache/incubator-nuttx/pull/6843
Please test to confirm it work for you before creating RC1.
BR,
Alan
On 8/12/22, alin.jerpe...@sony.com wrote:
> Hi Alan,
> Thanks for investigating the issue. Did you fix the hash ? Do you retract
> your -1 ?
>
> @
