Your "JSON" file isn't JSON, its full of escape character rubbish that are terminal control characters. Of course it will display in the terminal, but its not legal JSON. The crap includes many [
s and as the traceback shows the parser is looking for the matching ]
s recursively and running out of stack because all the [
s make it nested too deeply.
This is therefore not a bug.
#0 0x00007ffff7b39bad in matchRegex (line=0x13b9930, language=48)
at main/lregex.c:509
#1 0x00007ffff7b44dcb in iFileGetLine () at main/read.c:449
#2 0x00007ffff7b44eb0 in getcFromInputFile () at main/read.c:484
#3 0x00007ffff7b4528f in getcFromInputFile () at main/read.c:469
#4 0x00007ffff7b37385 in readTokenFull (token=token@entry=0x1442050, includeStringRepr=includeStringRepr@entry=false) at parsers/json.c:149
#5 0x00007ffff7b37645 in skipToOneOf3 (token=token@entry=0x1442050, type1=TOKEN_CLOSE_SQUARE, type2=TOKEN_EOF, type3=TOKEN_EOF) at parsers/json.c:246
#6 0x00007ffff7b37662 in skipToOneOf3 (token=token@entry=0x1442050, type1=TOKEN_CLOSE_SQUARE, type2=TOKEN_EOF, type3=TOKEN_EOF) at parsers/json.c:254
#7 0x00007ffff7b37662 in skipToOneOf3 (token=token@entry=0x1442050, type1=TOKEN_CLOSE_SQUARE, type2=TOKEN_EOF, type3=TOKEN_EOF) at parsers/json.c:254
#8
repeats until stack full.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.