Open axelson opened 6 years ago
That's a bit scary! It looks like a segfault in Go itself. I can't reproduce this on a 5.4mb 10k line jsonl file when building under Go 1.11, so maybe it has been fixed? Have you tried reinstalling ccat
with a newer version of Go?
How do I check what version ccat was compiled with? I don't see that in the output of ccat --version
. Also I'm still getting this on a 4.6M jsonl file on ccat v1.1.0.
Did you download ccat
from the releases page or install it yourself with go get
? If you installed it with go get
you can check by using go version
(provided you haven't updated Go since).
I installed via homebrew
Seems to happen the most on long "jsonl" files. That is a file with JSON that has a new JSON document on each line.
Here's an example stack trace: