-
Notifications
You must be signed in to change notification settings - Fork 13k
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
mingw-64 x86_64 toolchain gdb hangs during debuginfo tests #17540
Comments
To complete #16457 I'm just going to change |
For me it also hangs with GDB 7.6.1 from msys2. GDB seems to run into some kind of endless loop since it utilizes 100% of one CPU core. The freeze always happens when the debugger encounters the function Modifying the function to contain a call to |
This is what I found out so far:
I suspect that LLVM produces some kind of machine code sequence that GDB can't deal with, but it does so only for very small functions like My suggested way forward for next week:
|
Bug report about underlying GDB issue: |
…excrichton On some Windows versions of GDB this is more stable than setting breakpoints via function names. This is also something I wanted to do for some time now because it makes the tests more consistent. @brson: These changes are in response to issue #17540. It works on my machine with the toolchain mentioned in the issue. In order to find out if the problem is really worked around, we also need to make the build bots use the newer GDB version again.
@brson, |
@michaelwoerister it does not need to be fixed right now (though it would be good to fix). I will try switching the bots back to the other toolchain soon. |
OK, there's no hurry from my side. Just wanted to let you know that this should be a non-issue by now. |
Trying to switch the toolchain today. |
fingers crossed |
Done. Thanks @michaelwoerister |
On the bots, msys2 comes with version 7.6.1 of gdb. The installed x86_64-4.9.1-win32-seh-rt_v3-rev1 toolchain comes with gdb 7.8.1. When running the test suite with the latter, gdb hangs on all debuginfo tests; with the former it succeeds.
cc @michaelwoerister @vadimcn @klutzy
The text was updated successfully, but these errors were encountered: