On Tue, Sep 14, 2021 at 09:31:43PM +0200, Andreas Beck wrote:
> Package: ser2net
> Version: 3.5-2
> Severity: normal
>
> Dear Maintainer,
>
> I have been using ser2net to expose a device connected a serial port of
> microPC.
>
> As the original host application was showing some spurious errors on large
> transfers,
> I enabled tracelogs (see config below).
>
>
> The tracelogs showed strange behaviour: On a certain command, the device
> should have responded
> with a sequence of 2 replies, but the tracelogs showed basically a repeat of
> the first reply.
Yeah, this is already fixed in 3.5.1:
commit 34c5e9a5b44a3f57ad7dbf2ac3dfef8ffd68268c
Author: Corey Minyard <cminy...@mvista.com>
Date: Thu Aug 30 15:52:56 2018 -0500
Fix tracing of receive data
When tracing it wasn't taking into account the data already read.
Add "curend" to the data buf position.
Suggested-by: Brian Varney <brian.var...@broadcom.com>
Signed-off-by: Corey Minyard <cminy...@mvista.com>
Sorry about this, I know how frustrating it is if the tools aren't
reporting the right data.
It's a bummer you can't upgrade, there are other fixes that might be
relevant to you.
