-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a pretty bad bug report about a segfault, but at least I can show you the repo #18195
Comments
|
Thanks @hauntsaninja ! What did I do? :) |
Nothing you did! By default mypy ships binaries compiled with mypyc (these are 3-4x faster). In mypyc, stack overflows are segfaults, not nice RecursionError's. To get the RecursionError output, I ran pure Python mypy (you can As for what the code that mypy can't handle is, I haven't looked yet, but |
This commit glyph/Pomodouroboros@28da08a has a bunch of type errors, but mypy happily completes quickly again, and the most salient change is that I removed the use of |
I am at a bit of a loss as to what happened here, because I just noticed my editor's inline type-checking suddenly went away, and then saw a mypy process consuming an entire core for multiple minutes at a time, then crashing. I figured I'd get the report in quickly rather than try to minimize first, but I understand this is a pretty poor-quality bug report. The fact that the repo is open source might make it easy enough to get into a debugger for someone more knowledgeable.
Crash Report
zsh: segmentation fault mypy src
Traceback
it's a segfault so
--show-traceback
gives me nothing.To Reproduce
mypy src
onglyph/Pomodouroboros@8a8102c
Your Environment
mypy 1.13.0 (compiled: yes)
mypy.ini
(and other config files): see repoThe text was updated successfully, but these errors were encountered: