Hope this doesn't start to get annoying!
I captured two more cases for the received-wrong-and-duplicate case. Attached.
Also I couldn’t resist to create a PDF with some things highlighted ;-) Perhaps I should mention that for the PDF I:
* reversed the last-on-top output of sctestself
* removed the TX log lines of sctestself
* removed every send line of the candump log
For the last case, I attached debugger after the fail an tried to read from the socket until read returned -1:
(gdb) p malloc(72)
(gdb) p read(sockfd,$1,72)
(gdb) print fprint_canframe_mtu(stdout, $1, "\n", 4, 72) And surprise surprise, there were more CAN frames in store. Refer to the log/pdf.
-- Stefan
Attachment:
20230106T1822.tgz
Description: 20230106T1822.tgz
Attachment:
20230107T1352.tgz
Description: 20230107T1352.tgz
