From: Jan Vrany <jan@vrany.io>
To: Tom Tromey <tom@tromey.com>, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH RFC 0/2] Remove -readnow
Date: Wed, 11 Feb 2026 23:06:12 +0000 [thread overview]
Message-ID: <526e7045baa790b9913f77f7c03ffee9a38fc56b.camel@vrany.io> (raw)
On Wed, 2026-02-11 at 18:49 +0000, Tom Tromey wrote:
> [https://inbox.sourceware.org/gdb-patches/20260211-nuke-readnow-v1-0-7eed7148eec6@tromey.com/](https://inbox.sourceware.org/gdb-patches/20260211-nuke-readnow-v1-0-7eed7148eec6@tromey.com/)
>
> This short series removes the -readnow feature and then some
> supporting code.
>
> The justification is all in the first patch.
>
> Regression tested on x86-64 Fedora 40.
>
After applying both patches in this series, I get following
when running (for example) "make check TESTS=gdb.base/bfd-errors.exp"
---------
=== gdb tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/jv/Projects/gdb/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running /home/jv/Projects/gdb/gdb/testsuite/gdb.base/bfd-errors.exp ...
ERROR: tcl error sourcing /home/jv/Projects/gdb/gdb/testsuite/gdb.base/bfd-errors.exp.
ERROR: tcl error code NONE
ERROR: absolute path used
while executing
"error "absolute path used""
(procedure "clean_restart" line 28)
invoked from within
"clean_restart $binfile_lib"
(file "/home/jv/Projects/gdb/gdb/testsuite/gdb.base/bfd-errors.exp" line 150)
invoked from within
"source /home/jv/Projects/gdb/gdb/testsuite/gdb.base/bfd-errors.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source /home/jv/Projects/gdb/gdb/testsuite/gdb.base/bfd-errors.exp"
invoked from within
"catch "uplevel #0 source $test_file_name" msg"
PATH: gdb.base/bfd-errors.exp: testcase '/home/jv/Projects/gdb/gdb/testsuite/gdb.base/bfd-errors.exp' aborted due to Tcl error
=== gdb Summary ===
# of unresolved testcases 1
# of paths in test names 1
---------
I see this is happening for
gdb.base/bfd-errors.exp
gdb.dwarf2/dw2-icycle.exp
gdb.dwarf2/dwznolink.exp
gdb.dwarf2/multidictionary.exp
gdb.dwarf2/nostaticblock.exp
In gdb.dwarf2/nostaticblock.exp I also see:
-------
ERROR: -------------------------------------------
ERROR: in testcase /home/jv/Projects/gdb/users_jv_patches/gdb/testsuite/gdb.dwarf2/nostaticblock.exp
ERROR: can't read "executable": no such variable
ERROR: tcl error code TCL LOOKUP VARNAME executable
ERROR: tcl error info:
can't read "executable": no such variable
while executing
"clean_restart $executable"
(file "/home/jv/Projects/gdb/users_jv_patches/gdb/testsuite/gdb.dwarf2/nostaticblock.exp" line 41)
invoked from within
"source /home/jv/Projects/gdb/users_jv_patches/gdb/testsuite/gdb.dwarf2/nostaticblock.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source /home/jv/Projects/gdb/users_jv_patches/gdb/testsuite/gdb.dwarf2/nostaticblock.exp"
invoked from within
"catch "uplevel #0 source $test_file_name" msg"
-------
Running on Debian 13 x86_64.
Jan
next reply other threads:[~2026-02-11 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 23:06 Jan Vrany [this message]
2026-02-12 2:31 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2026-02-11 18:49 Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=526e7045baa790b9913f77f7c03ffee9a38fc56b.camel@vrany.io \
--to=jan@vrany.io \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox