-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
Fixes bugs found by pyfailmalloc during Python initialization #62720
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
Comments
I'm working on a version of pyfailmalloc integrated into CPython to inject memory allocation failures duging Python startup. As expected, I found new bugs. I create this issue to track these bugs and their fix, as I did with the issue bpo-18408. Home page of the project: |
New changeset 276477d5a548 by Victor Stinner in branch 'default': |
PyStructSequence_InitTypeWithError() return type is void, whereas it can fail and raise an exception. Can I change the return type, or should I create a new function? |
New changeset fc718c177ee6 by Victor Stinner in branch 'default': New changeset 9b77b3ee6fb8 by Victor Stinner in branch 'default': New changeset 31796b188bec by Victor Stinner in branch 'default': New changeset d38348173c46 by Victor Stinner in branch 'default': New changeset 9267a0b836b7 by Victor Stinner in branch 'default': New changeset 4a69dbe71aeb by Victor Stinner in branch 'default': New changeset a4998e8fd7fc by Victor Stinner in branch 'default': |
I ran my test for more than 30 minutes and I didn't find any interesting bug anymore, so I'm closing the issue. |
Victor, could you look at the end of bpo-10241? Starting from 31796b188bec, |
New changeset 5eb00460e6e8 by Victor Stinner in branch 'default': |
It was a mistake, it should now be fixed. Nice catch. |
Ah, thanks. I was wondering if there was some obscure reason that escaped me. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: