Skip to content
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

Jump to bottom

Spurious gdb failed to execute on Windows #42693

Open
arielb1 opened this issue Jun 16, 2017 · 1 comment
Open

Spurious gdb failed to execute on Windows #42693

arielb1 opened this issue Jun 16, 2017 · 1 comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-enhancement Category: An issue proposing an enhancement or a PR with one. O-windows-gnu Toolchain: GNU, Operating system: Windows T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue.

Comments

@arielb1
Copy link
Contributor

arielb1 commented Jun 16, 2017 •
edited

First seen in #41840 - https://ci.appveyor.com/project/rust-lang/rust/build/1.0.3595/job/4s8ofgv42um1t8b2:

failures:
---- [debuginfo-gdb] debuginfo-gdb\borrowed-c-style-enum.rs stdout ----
	NOTE: compiletest thinks it is using GDB without native rust support
NOTE: compiletest thinks it is using GDB version 7010001
error: gdb failed to execute
thread '[debuginfo-gdb] debuginfo-gdb\borrowed-c-style-enum.rs' panicked at 'explicit panic', src\tools\compiletest\src\runtest.rs:1651
@arielb1 arielb1 added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Jun 16, 2017
@arielb1 arielb1 mentioned this issue Jun 16, 2017
Merged
This was referenced Jun 26, 2017
Merged
Merged
frewsxcv added a commit to frewsxcv/rust that referenced this issue Jun 27, 2017
@frewsxcv
Rollup merge of rust-lang#42917 - kennytm:gdb-fatal-proc-rec, r=Mark-…
d7a5508 
…Simulacrum

compiletest: show details why GDB failed to execute.

Help finding reasons of spurious errors due to GDB failing to run (rust-lang#42693).
@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label Jul 27, 2017
@kennytm kennytm mentioned this issue Sep 3, 2017
Merged
@kennytm
Copy link
Member

kennytm commented Sep 3, 2017

The error code from #44261 is 1816, which is ERROR_NOT_ENOUGH_QUOTA (Not enough quota is available to process this command.)

@kennytm kennytm mentioned this issue Oct 12, 2017
Open
@kennytm kennytm mentioned this issue Jan 8, 2018
Merged
@kennytm kennytm mentioned this issue Jun 8, 2018
Merged
@joshtriplett joshtriplett removed the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label Jun 25, 2018
@XAMPPRocky XAMPPRocky added O-windows Operating system: Windows C-enhancement Category: An issue proposing an enhancement or a PR with one. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. labels Jun 26, 2018
@kennytm kennytm mentioned this issue Sep 7, 2018
Merged
@wesleywiser wesleywiser added O-windows-gnu Toolchain: GNU, Operating system: Windows and removed O-windows Operating system: Windows labels Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-enhancement Category: An issue proposing an enhancement or a PR with one. O-windows-gnu Toolchain: GNU, Operating system: Windows T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@kennytm @joshtriplett @wesleywiser @arielb1 @XAMPPRocky @Mark-Simulacrum