arach)
Cc: Christian Hopps ; vpp-dev
Subject: Re: [vpp-dev] debugging corrupted frame arguments
> On Jul 23, 2020, at 4:09 PM, Dave Barach via lists.fd.io
> wrote:
>
[ swapped the order of my reply :) ]
> Without having all of the source code available and a reasonable way to r
er variation I can try is to run the tunnel a bit faster and slower to
increase the per call packet count to see if the corruption moves away from the
4th element.
Thanks,
Chris.
>
> D.
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of Christian Hopps
> S
t.
D.
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Christian Hopps
Sent: Thursday, July 23, 2020 1:10 PM
To: vpp-dev
Cc: Christian Hopps
Subject: [vpp-dev] debugging corrupted frame arguments
I have a very intermittent memory corruption occurring in the buffer indices
passed
c: Christian Hopps
> Subject: [vpp-dev] debugging corrupted frame arguments
>
> I have a very intermittent memory corruption occurring in the buffer
> indices passed in a nodes frame (encryption node).
>
> Basically one of the indices is clearly not a vadlid buffer index, and
> thi
I have a very intermittent memory corruption occurring in the buffer indices
passed in a nodes frame (encryption node).
Basically one of the indices is clearly not a vadlid buffer index, and this is
leading to a SIGSEGV when the code attempts to use the buffer.
I see that vlib_frame_ts are allo
