Open benknoble opened 1 month ago
Hello. Thanks for submitting this. Does this occur when you run proselint --demo
, or proselint /path/to/file
instead of proselint </path/to/file
?
Hello. Thanks for submitting this. Does this occur when you run
proselint --demo
, orproselint /path/to/file
instead ofproselint </path/to/file
?
Interesting:
proselint --demo
succeedsproselint /dev/null
segfaultsproselint /path/to/real/markdown/file
segfaults, except when that path is to the demo file (like /usr/local/Cellar/proselint/0.14.0/libexec/lib/python3.12/site-packages/proselint/demo.md
). It doesn't appear to matter if the path is in ~
, /tmp
, or /usr/local
.That is interesting indeed. Does the same issue occur for regular text files, or just markdown files that happen to not be the demo for some reason?
Yes, this occurs on other plaintext files
I'm reliably seeing a segmentation fault. Here's Apple's report:
And system specs:
I have
proselint
installed by Homebrew; I tried bothbrew reinstall python3 proselint
andbrew reinstall --build-from-source proselint
and always get the segfault:Please let me know what other information would be helpful. I can try to set
ulimit
to dump core and attach a debugger if necessary, but I'm not particularly experienced at that.