build v3.13.0rc1 on windows failed with -1073741819 error code.
#123414
Labels
Comments
|
Here is some suggestions from GPT4. The error code The fact that the error is pointing to Possible Causes
Steps to Troubleshoot
Would you like to perform a specific troubleshooting step, or do you need help with debugging the issue further? |
|
|
|
I see some errors like Any ideas?
|
|
I'm not all that familiar with the Windows build, but out of curiosity, does this occur (or possibly, give a more insightful error) when using a debug build? ( |
@ZeroIntensity I tried to build a debug build in the visual studio, but it's the same. |
|
A Visual Studio trace (in particular, the full call stack) of the 32-bit build would be most interesting. The screenshot you've shown is a 64-bit build. In either case, what's most likely is that you've got some app on your Also, in future, don't bother pasting AI chat bot output here. They base their information off thing that we ourselves have written down (you'll notice that it suggests the same things as I just did). So check it and follow it, by all means, but no need to give our words back to us. |
|
I tested building via visual studio gui or pcbuild.bat for both 32 and 64 bit, it's just the same error. The build python.exe binary not working, exited with the same error code. But when I replaced python313.dll with the official build, it's working. So maybe it's not PATH issues. The two dll files are attached above, is there any method or tools to compare them. |
Only by running until yours breaks and tracing how it got there. When I run my own 32-bit build of 3.13.0rc1, everything works. For it to be building differently, you must have a different compiler, or have some other environment variables set that are affecting the includes or libraries it is linking to. Perhaps if you post your entire environment when you build (either |
|
@zooba Hi, here is my environments and reproduce steps. I use dumpbin to check the exports of the two dlls. It's quite different.
DetailsAnd I also tried to build it via Details |
Those look much the same to me. The one you built will have debug symbols handy, which is why it shows more information. The only thing I can think of is interference from a past build, so a Other than that, diagnosing the cause of the crash (where the invalid pointer is coming from) is probably the way forward. Knowing that it's a build related issue helps, but we still need to know which bit of code is behaving badly. |
|
Any updates on this? Or should I do a bisect? |
|
What is there to bisect? I don't think @zooba was able to reproduce this. |
|
I'm getting the same error... |
|
The same exit code, or a failure at that same line? If it's the latter, then it would be great to try and diagnose the problem. |
|
I'm getting the same exit code, I'll check what happens if I run the same command. |
|
|
|
I suspect that return code is some sort of blanket for "something went horribly wrong," probably not the same issue. I'd follow Steve's suggestions and trying rebuilding with a fresh clone. |
|
Should I reinstall Visual Studio build tools for Python too? |
|
Ah, that was it. I must have broken something while bisecting. |
|
I think this is just collecting dust and leads to false-positives with bug reports, so I'm going to close this for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
I tried to build 3.13.0rc1 on windows via
call Tools\msi\buildrelease.bat -x86 -b. But it failed with the following error messages.I found the following errors on Event Viewer.
I found it's the "D:\code\python\windows-python-installer\cpython\Tools\msi....\PCbuild\win32\python.exe" binary could not run. And if I replace
python313.dllwith the offical one, then it worked.It's really strange. I didn't change any lines of code of v3.13.0rc1 tag.
python313.zip
CPython versions tested on:
3.13
Operating systems tested on:
Windows
The text was updated successfully, but these errors were encountered: