Hi Tom,
On Mon, 2020-10-26 at 16:54 -0600, Tom Tromey wrote:
> > > In this patch, I chose to try to handle weird leb128 encodings by
> > > preserving their values when possible; or returning the maximum value
> > > on overflow. It isn't clear to me that this is necessarily the best
> > > choice.
>> In this patch, I chose to try to handle weird leb128 encodings by
>> preserving their values when possible; or returning the maximum value
>> on overflow. It isn't clear to me that this is necessarily the best
>> choice.
Mark> I think it is a good thing to accept "padded" leb128 numbers, but
M
Hi Tom,
On Fri, Oct 23, 2020 at 09:58:34PM -0600, Tom Tromey wrote:
> PR 26773 points out that some sleb128 values are decoded incorrectly.
> Looking into this, I found some other unusual cases as well.
>
> In this patch, I chose to try to handle weird leb128 encodings by
> preserving their value
