Re: close() socket called in second thread combined with reconnect kills eth (stm32h743zi)

2020-07-09 Thread Reto Gähwiler
Good Morning Everyone, First of all, thanks for your responses. We eventually will change the design and handle recv and close in the same pthread and follow your advices, Xiang Xiao / Nathan Hartman. @Gregory Nutt: Yes, I was meaning the same pthread. Technically, the pthread calling the

RE: close() socket called in second thread combined with reconnect kills eth (stm32h743zi)

2020-07-06 Thread Xiang Xiao
> -Original Message- > From: Reto Gähwiler > Sent: Tuesday, June 30, 2020 4:58 PM > To: dev@nuttx.apache.org > Subject: close() socket called in second thread combined with reconnect kills > eth (stm32h743zi) > > Hello Everyone, > > I am facing

Re: close() socket called in second thread combined with reconnect kills eth (stm32h743zi)

2020-07-06 Thread Gregory Nutt
On 6/30/2020 2:58 AM, Reto Gähwiler wrote: Hello Everyone, I am facing the following problem working with nuttx and ethernet connections. A TCP socket is setup as blocking and connected to the server. The connection is handled in one thread which hangs in the recv call and processes the data if

Re: close() socket called in second thread combined with reconnect kills eth (stm32h743zi)

2020-07-06 Thread Nathan Hartman
Ping... this question seemed to be waiting on our mailing list for several days: On Tue, Jun 30, 2020 at 4:58 AM Reto Gähwiler wrote: > I am facing the following problem working with nuttx and ethernet > connections. A TCP socket is setup as blocking and connected to the server. > The connection

close() socket called in second thread combined with reconnect kills eth (stm32h743zi)

2020-06-30 Thread Reto Gähwiler
Hello Everyone, I am facing the following problem working with nuttx and ethernet connections. A TCP socket is setup as blocking and connected to the server. The connection is handled in one thread which hangs in the recv call and processes the data if some arrives. In case of an error the