mypy 1.7.0 crashes (segmentation fault) #16450
Labels
Comments
|
output of mypy with --verbose: https://gist.github.com/jepler/6087e5ba5e9b0298f7ceecc416a68bc5 |
|
Thanks for the crash report! Can you check if using |
|
That flag doesn't change the outcome: the gdb stack-trace and the |
|
Minimized test case: |
|
And the truly minimized test case: """ A Partial helper that can be used to add arguments for an arbitrary class or callable. """
from typing import Callable
from typing_extensions import TypeVar
_T = TypeVar("_T", bound=Any)
class Partial:
def __call__(self: Callable[..., None]) -> _T:
...This is of course nonsense since _T doesn't appear on the left, but the segmentation fault should probably still not occur. |
|
The slightly less nonsense |
|
Interpreted version results in It is likely caused by one of my PRs (where I enabled |
|
Thank you! |
|
@ilevkivskyi Using my truly minimized example and git bisect, I believe the problem may have been introduced at commit f41e24c: edited to add git bisect log: |
ilevkivskyi
added a commit
that referenced
this issue
Nov 11, 2023
Fixes #16450 The fix is a bit ad-hoc, but OTOH there is nothing meaningful we can infer in such situation, so it is probably OK.
JukkaL
pushed a commit
that referenced
this issue
Nov 22, 2023
Fixes #16450 The fix is a bit ad-hoc, but OTOH there is nothing meaningful we can infer in such situation, so it is probably OK.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
mypy 1.7.0 exits with a segmentation fault analyzing code that passed under 1.6.1
To Reproduce
I do not have a minimized test case at this point.
Expected Behavior
Actual Behavior
Segmentation fault. The cause seems to be unbounded recursion, as shown in this partial gdb backtrace:
Your Environment
mypy -p chapThe text was updated successfully, but these errors were encountered: