-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/build: Add gdb to Windows Builders #22021
Comments
@johnsonj while you at it ... 2 out of 5 gdb tests are skipped on my computer:
I suspect it would be hard to make skipped tests run. As far as I remember I tried some time ago and failed. Do not spent too much time on it if you cannot. Alex |
Change https://go.dev/cl/470596 mentions this issue: |
@thanm @dmitshur if approved, CL 470596 will unskip all gdb test on Windows. I've tried with gdb 12.1 and all tests passes. Is it time to add gdb to Windows builders? I'm particularly interested on this because I want to add some CGO unwinding tests as part of #58378, and they ideally should also run on Windows using gdb and SEH (once #57302 is done). |
Seems ok to me on principle. What distribution/vintage of GDB 12 did you use for your testing? |
Note to self: while we are installing GDB, it would probably also be a good idea to install Delve as well (right now I don't think there are any tests that use delve that run on windows, but this could change). |
The one you get from running $ gcc --version
gcc.exe (MinGW-W64 x86_64-ucrt-posix-seh, built by Brecht Sanders) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gdb --version
GNU gdb (GDB for MinGW-W64 x86_64, built by Brecht Sanders) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. |
The runtime-gdb.py script needs procid to be set in order to map a goroutine ID with an OS thread. The Go runtime is not currently setting that variable on Windows, so TestGdbPython (and friends) can't succeed. This CL initializes procid and unskips gdb tests on Windows. Fixes #22687 Updates #21380 Updates #22021 Change-Id: Icd1d9fc1764669ed1bf04f53d17fadfd24ac3f30 Reviewed-on: https://go-review.googlesource.com/c/go/+/470596 Reviewed-by: Alex Brainman <alex.brainman@gmail.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Quim Muntal <quimmuntal@gmail.com>
Change https://go.dev/cl/473116 mentions this issue: |
TestGdbPanic expects crash() to raise a SIGABRT signal interceptable by gdb, but Windows doesn't have signals. Windows builders haven't caught this failing test because they still don't have gdb installed (tracked in #22021). Change-Id: I7c7f2523a54d61aea0a9821c4db7c79e58a7217c Reviewed-on: https://go-review.googlesource.com/c/go/+/473116 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Quim Muntal <quimmuntal@gmail.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Quim Muntal <quimmuntal@gmail.com>
As observed in #22012 the Windows builders do not have gdb causing them to skip any gdb related test.
Add gdb to these packages
The text was updated successfully, but these errors were encountered: