On 12/09/2011 02:41 PM, k...@ixxat.de wrote: > I noticed that when libsocketcan calls send_dump_request() it returns a > message for me that has a length of 3424 with recvmsg(). This is not the > full message, if I add a loop into the routine to again receive, I receive a > second message this time with a length of 1424. I added some prints into the > routine to output strings and sizes: > > First read: > nl_msg:-1073753668 u_msglen:3424 > lo > nl_msg:-1073752676 u_msglen:2432 > eth0 > nl_msg:-1073751668 u_msglen:1424 > can0 > nl_msg:-1073750956 u_msglen:712 > can1 > > Second read: > nl_msg:-1073753668 u_msglen:1424 > can2 > nl_msg:-1073752956 u_msglen:712 > can3 > > With this loop, it seems to work. Does this make sense?
Yes, could you send a patch (showing your modifications)? Wolfgang. _______________________________________________ Socketcan-core mailing list Socketcan-core@lists.berlios.de https://lists.berlios.de/mailman/listinfo/socketcan-core
