Hello, > When i use lwip_send(), the copy of the buffer parameter is copied during > the lwip processing of the message. This leads to make the following code > being random :
Did you mean "is not copied"? Becasue if it is, it should not happen your previous scenario. Is your connection TCP? I did not inspect it deeply but on line 771 of sockets.c(lwip 1.4.1) for e.g. UDP the NETCONN_COPY is not set by default. Best Martin On Sat, May 25, 2013 at 8:45 PM, Laurent <[email protected]> wrote: > Hi, > > I'm currently porting Lwip 1.4.1 to ALMOS (an open-source research operating > system currently under development aiming cc-NUMA Architecture, if you want > to learn about it you can find it at https://www.almos.fr/trac/almos > <https://www.almos.fr/trac/almos> ) > I'm using Lwip-thread to handle TCP/IP Connection. I run into a problem when > using the socket API provided. > > When i use lwip_send(), the copy of the buffer parameter is copied during > the lwip processing of the message. This leads to make the following code > being random : > > lwip_send(fd,buf,size,0); > memset(buf,0,size); > > It can send a buffer full of zeros, a buffer half of zeros, or the buffer > with nice datas. I'm pretty sure the Socket API ensure a sequential > execution. Did anyone run into that problem and is there a fix for this? > > > > -- > View this message in context: > http://lwip.100.n7.nabble.com/Socket-Api-send-copy-tp21449.html > Sent from the lwip-users mailing list archive at Nabble.com. > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
