-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Segfault when using improperly defined struct #53754
Comments
On master I don't get a segfault but I still get an internal error. |
Originally I wanted to only assign the global |
Time to revisit #32658? |
I think if we could fix dispatch with malformed types to go to the kind instead, we could treat these as malformed types which have inference disabled on them (instead of as concrete types) until the fields get populated? I am still not exactly sure of the details of that though. Is there some part of #32658 we should try to merge and backport now? |
The easier version of this is to just never populate the field types, and you have to reload the module and try again. |
Currently, these cases do indeed cause a segfault, so how about adjusting some critical functions to avoid a segfault and at least keep the session alive? |
When defining a struct that uses a type that doesn't exist, you get an error but the struct is still somehow defined. Using it then causes a crash. I would expect the struct to not be defined at all, or at least using it to be an error not a crash.
The text was updated successfully, but these errors were encountered: