Odd behavior using jshon

[apmilen]

Not really sure what's going on here. I built jshon from this release and get this result when testing it:

$ jshon -e foo <<< '{"foo":"ay4d748edadf7"}'
json read error: line 2 column 1: end of file expected near '_'

however if the string is just one character shorter, it works fine:

$ jshon -e foo <<< '{"foo":"ay4d748edadf"}'
"ay4d748edadf"

another experiment yields a different error:

$ echo -n '{"foo":"ay4d748df7"}' | jshon -e foo
json read error: line 1 column 20: unable to decode byte 0xff

Any idea what might be going wrong?

[NiklasKunkel]

Have this exact same issue.

[mbrock]

I could only reproduce this on my OS X computer.

Basically jshon tries to parse extra garbage when you give it a file or stdin, because it doesn't properly null-terminate its input.

On OS X it seems to happen only when the input size is 15 bytes or bigger (probably because of some intricacies of malloc), while on Linux I seem to always get a pre-zeroed buffer so the problem doesn't show up.

[dbrock]

Bump

[ldanicel]

Double Bump

[keenerd]

Fixed with d919aea. Thank you mbrock.