-
Notifications
You must be signed in to change notification settings - Fork 12.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
mingw-w64: Most debuginfo-gdb
tests fail with new GDB 7.11.1
#40184
Comments
Workaround:
|
It looks like if the 6.3.0 gdb is run manually it produces the expected output, it's just when called by the build system that it fails as indicated. |
This is specifically caused when the stdin to the gdb process is a pipe, not inherited. I have absolutely no clue why. I've got a patch to fix though that'll go in #40777 |
There's a cygwin mailing list thread that looks related: https://cygwin.com/ml/cygwin/2016-10/msg00235.html. |
From the mailing list:
Anyone with a working |
It looks like the 6.3.0 MinGW comes with a gdb which has issues (rust-lang#40184) that an attempted workaround (rust-lang#40777) does not actually fix (rust-lang#40835). The original motivation for upgradin MinGW was to fix build flakiness (rust-lang#40546) due to newer builds not exhibiting the same bug, so let's hope that 6.2.0 isn't too far back in time and still contains the fix we need. Closes rust-lang#40835
…elb1 appveyor: Downgrade MinGW to 6.2.0 It looks like the 6.3.0 MinGW comes with a gdb which has issues (rust-lang#40184) that an attempted workaround (rust-lang#40777) does not actually fix (rust-lang#40835). The original motivation for upgradin MinGW was to fix build flakiness (rust-lang#40546) due to newer builds not exhibiting the same bug, so let's hope that 6.2.0 isn't too far back in time and still contains the fix we need. Closes rust-lang#40835
This commit sort of brings back rust-lang#40777 by upgrading back to 6.3.0. While investigating rust-lang#40546 it was discovered that 6.3.0 appears to not spurious fail in the same way that 6.2.0 does (which we're currently using). The workaround for rust-lang#40184 contained in rust-lang#40777 did not work so this commit also contains a different workaround for the gdb issue. We will not download the 6.2.0 version of gdb and use that instead of the default version that comes with 6.3.0. I'm going to optimistically say... Closes rust-lang#40546
…enkov appveyor: Upgrade to gcc for mingw 6.3.0 This commit sort of brings back rust-lang#40777 by upgrading back to 6.3.0. While investigating rust-lang#40546 it was discovered that 6.3.0 appears to not spurious fail in the same way that 6.2.0 does (which we're currently using). The workaround for rust-lang#40184 contained in rust-lang#40777 did not work so this commit also contains a different workaround for the gdb issue. We will not download the 6.2.0 version of gdb and use that instead of the default version that comes with 6.3.0. I'm going to optimistically say... Closes rust-lang#40546
This commit sort of brings back rust-lang#40777 by upgrading back to 6.3.0. While investigating rust-lang#40546 it was discovered that 6.3.0 appears to not spurious fail in the same way that 6.2.0 does (which we're currently using). The workaround for rust-lang#40184 contained in rust-lang#40777 did not work so this commit also contains a different workaround for the gdb issue. We will not download the 6.2.0 version of gdb and use that instead of the default version that comes with 6.3.0. I'm going to optimistically say... Closes rust-lang#40546
appveyor: Upgrade to gcc for mingw 6.3.0 This commit sort of brings back #40777 by upgrading back to 6.3.0. While investigating #40546 it was discovered that 6.3.0 appears to not spurious fail in the same way that 6.2.0 does (which we're currently using). The workaround for #40184 contained in #40777 did not work so this commit also contains a different workaround for the gdb issue. We will not download the 6.2.0 version of gdb and use that instead of the default version that comes with 6.3.0. I'm going to optimistically say... Closes #40546
|
Fixed starting with |
If you recently updated mingw version to
x86_64-6.3.0-win32-seh-rt_v5-rev1
or just updated packages in MSYS2 you may discover this unpleasant surprise:or even worse (with MSYS subsystem gdb)
The text was updated successfully, but these errors were encountered: