Geir wrote: > This is a potential race > condition as the semaphore is deleted prior to the conn->sem being set > to 0 in netconn_write. The lwip_thread runs at a higher task priority > than the application thread and may interrupt the application thread > between the delete and and the 0 assignment. I fixed this in my > application by removing the semaphore deletion/assignment from > netconn_write and have the semaphore exist until netconn_delete is called.
Added this change to our CVS HEAD. Note there are more issues with the netconn_* stuff that I listed as bug #15926 (and added to the TODO list in the CHANGELOG). Thanks for reporting. Christiaan Simons Hardware Designer Axon Digital Design http://www.axon.tv _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
