Repository navigation
Open
Labels
A-debuggersArea: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)Area: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)A-debuggers-gdbArea: gdbArea: gdbA-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.I-flaky-testIssue: A test is flaky/unreliable/spuriously failsIssue: A test is flaky/unreliable/spuriously failsT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
See:
/checkout/obj/build/x86_64-unknown-linux-gnu/test/debuginfo/function-call.gdb/function-call.debugger.script:11: Error in sourced command file:
Couldn't write extended state status: Bad address.
Log
---- [debuginfo-gdb] tests/debuginfo/function-call.rs stdout ----
NOTE: compiletest thinks it is using GDB version 12001000
------gdb stdout------------------------------
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04.2) 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.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Breakpoint 1 at 0x1b42: file /checkout/tests/debuginfo/function-call.rs, line 36.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Breakpoint 1, function_call::main () at /checkout/tests/debuginfo/function-call.rs:36
36 zzz(); // #break
------gdb stderr------------------------------
/checkout/obj/build/x86_64-unknown-linux-gnu/test/debuginfo/function-call.gdb/function-call.debugger.script:11: Error in sourced command file:
Couldn't write extended state status: Bad address.
------------------------------------------
error: gdb failed to execute
status: exit status: 1
command: PYTHONPATH="/checkout/src/etc" "/usr/bin/gdb" "-quiet" "-batch" "-nx" "-command=/checkout/obj/build/x86_64-unknown-linux-gnu/test/debuginfo/function-call.gdb/function-call.debugger.script"
--- stdout -------------------------------
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04.2) 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.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Breakpoint 1 at 0x1b42: file /checkout/tests/debuginfo/function-call.rs, line 36.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Breakpoint 1, function_call::main () at /checkout/tests/debuginfo/function-call.rs:36
36 zzz(); // #break
------------------------------------------
--- stderr -------------------------------
/checkout/obj/build/x86_64-unknown-linux-gnu/test/debuginfo/function-call.gdb/function-call.debugger.script:11: Error in sourced command file:
Couldn't write extended state status: Bad address.
------------------------------------------
---- [debuginfo-gdb] tests/debuginfo/function-call.rs stdout end ----
failures:
[debuginfo-gdb] tests/debuginfo/function-call.rs
test result: FAILED. 148 passed; 1 failed; 24 ignored; 0 measured; 0 filtered out; finished in 9.02s
Some tests failed in compiletest suite=debuginfo mode=debuginfo host=x86_64-unknown-linux-gnu target=x86_64-unknown-linux-gnu
Bootstrap failed while executing `--stage 2 test`
Build completed unsuccessfully in 0:34:52
Metadata
Metadata
Assignees
Labels
A-debuggersArea: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)Area: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)A-debuggers-gdbArea: gdbArea: gdbA-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.I-flaky-testIssue: A test is flaky/unreliable/spuriously failsIssue: A test is flaky/unreliable/spuriously failsT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Activity
jieyouxu commentedon Jul 16, 2026
#159401 gates this test with min GDB 15.1 that I can't reproduce the failure locally with. CI as of time of writing typically uses GDB 12.1 under Ubuntu 22.04, so the min GDB gate kicks it out of CI but still lets it run locally with GDB >= 15.1.
Rollup merge of rust-lang#159401 - jieyouxu:jieyouxu/test/function-ca…
Rollup merge of rust-lang#159401 - jieyouxu:jieyouxu/test/function-ca…
Rollup merge of rust-lang#159401 - jieyouxu:jieyouxu/test/function-ca…
Rollup merge of rust-lang#159401 - jieyouxu:jieyouxu/test/function-ca…
Unrolled build for #159401
jieyouxu commentedon Jul 19, 2026
See investigation at: #t-compiler > `tests/debuginfo/function-call.rs` + gdb recently flaky @ 💬
It's quite likely that the gdb version 12.1 we use in CI doesn't support the hardware of the CI runners (well), i.e. processors
which are released later than gdb 12.1.