From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/5] [gdb] xml linting
Date: Wed, 26 Aug 2026 23:22:04 +0200 [thread overview]
Message-ID: <20260826212209.925066-1-tdevries@suse.de> (raw)
This contains five patches.
The first patch adds two pre-commit checks for xml files.
The following patch fixes a namespace problem found with xmllint.
The third and fourth patches fix problems found with xmllint --valid.
The last patch enables xmllint --valid for clean files.
Changes in v2:
- fix bug in in the second patch: don't add <target> ... </target>
- in the first patch, add xmllint disabled by default (stages: manual)
- add two patches fixing problems found using xmllint --valid
- add a patch enabling xmllint --valid
Versions:
- v1 https://sourceware.org/pipermail/gdb-patches/2026-August/229764.html
Tom de Vries (5):
[pre-commit] Check xml files
[gdb] Fix xmllint namespace errors
[gdb] Fix target element validity error in features/gdb-target.dtd
[gdb] Fix syscalls-info -> syscalls_info in syscalls/gdb-syscalls.dtd
[pre-commit] Use --valid with xmllint
.pre-commit-config.yaml | 27 ++++
gdb/contrib/xmllint.sh | 152 ++++++++++++++++++
gdb/features/alpha.xml | 2 +-
gdb/features/gdb-target.dtd | 6 +-
gdb/features/microblaze-linux.xml | 2 +-
.../microblaze-with-stack-protect.xml | 2 +-
gdb/features/microblaze.xml | 2 +-
gdb/features/mips-dsp-linux.xml | 2 +-
gdb/features/mips-linux.xml | 2 +-
gdb/features/mips64-dsp-linux.xml | 2 +-
gdb/features/mips64-linux.xml | 2 +-
gdb/features/nds32.xml | 2 +-
gdb/features/or1k-linux.xml | 2 +-
gdb/features/or1k.xml | 2 +-
gdb/features/rs6000/powerpc-32.xml | 2 +-
gdb/features/rs6000/powerpc-32l.xml | 2 +-
gdb/features/rs6000/powerpc-403.xml | 2 +-
gdb/features/rs6000/powerpc-403gc.xml | 2 +-
gdb/features/rs6000/powerpc-405.xml | 2 +-
gdb/features/rs6000/powerpc-505.xml | 2 +-
gdb/features/rs6000/powerpc-601.xml | 2 +-
gdb/features/rs6000/powerpc-602.xml | 2 +-
gdb/features/rs6000/powerpc-603.xml | 2 +-
gdb/features/rs6000/powerpc-604.xml | 2 +-
gdb/features/rs6000/powerpc-64.xml | 2 +-
gdb/features/rs6000/powerpc-64l.xml | 2 +-
gdb/features/rs6000/powerpc-7400.xml | 2 +-
gdb/features/rs6000/powerpc-750.xml | 2 +-
gdb/features/rs6000/powerpc-860.xml | 2 +-
gdb/features/rs6000/powerpc-altivec32.xml | 2 +-
gdb/features/rs6000/powerpc-altivec32l.xml | 2 +-
gdb/features/rs6000/powerpc-altivec64.xml | 2 +-
gdb/features/rs6000/powerpc-altivec64l.xml | 2 +-
gdb/features/rs6000/powerpc-e500.xml | 2 +-
gdb/features/rs6000/powerpc-e500l.xml | 2 +-
gdb/features/rs6000/powerpc-isa205-32l.xml | 2 +-
gdb/features/rs6000/powerpc-isa205-64l.xml | 2 +-
.../rs6000/powerpc-isa205-altivec32l.xml | 2 +-
.../rs6000/powerpc-isa205-altivec64l.xml | 2 +-
.../rs6000/powerpc-isa205-ppr-dscr-vsx32l.xml | 2 +-
.../rs6000/powerpc-isa205-ppr-dscr-vsx64l.xml | 2 +-
gdb/features/rs6000/powerpc-isa205-vsx32l.xml | 2 +-
gdb/features/rs6000/powerpc-isa205-vsx64l.xml | 2 +-
.../rs6000/powerpc-isa207-htm-vsx32l.xml | 2 +-
.../rs6000/powerpc-isa207-htm-vsx64l.xml | 2 +-
gdb/features/rs6000/powerpc-isa207-vsx32l.xml | 2 +-
gdb/features/rs6000/powerpc-isa207-vsx64l.xml | 2 +-
gdb/features/rs6000/powerpc-vsx32.xml | 2 +-
gdb/features/rs6000/powerpc-vsx32l.xml | 2 +-
gdb/features/rs6000/powerpc-vsx64.xml | 2 +-
gdb/features/rs6000/powerpc-vsx64l.xml | 2 +-
gdb/features/rs6000/rs6000.xml | 2 +-
gdb/features/rx.xml | 2 +-
gdb/features/s390-gs-linux64.xml | 2 +-
gdb/features/s390-linux32.xml | 2 +-
gdb/features/s390-linux32v1.xml | 2 +-
gdb/features/s390-linux32v2.xml | 2 +-
gdb/features/s390-linux64.xml | 2 +-
gdb/features/s390-linux64v1.xml | 2 +-
gdb/features/s390-linux64v2.xml | 2 +-
gdb/features/s390-te-linux64.xml | 2 +-
gdb/features/s390-tevx-linux64.xml | 2 +-
gdb/features/s390-vx-linux64.xml | 2 +-
gdb/features/s390x-gs-linux64.xml | 2 +-
gdb/features/s390x-linux64.xml | 2 +-
gdb/features/s390x-linux64v1.xml | 2 +-
gdb/features/s390x-linux64v2.xml | 2 +-
gdb/features/s390x-te-linux64.xml | 2 +-
gdb/features/s390x-tevx-linux64.xml | 2 +-
gdb/features/s390x-vx-linux64.xml | 2 +-
gdb/features/sparc/sparc32-solaris.xml | 2 +-
gdb/features/sparc/sparc64-solaris.xml | 2 +-
gdb/features/tic6x-c62x-linux.xml | 2 +-
gdb/features/tic6x-c64x-linux.xml | 2 +-
gdb/features/tic6x-c64xp-linux.xml | 2 +-
gdb/features/z80.xml | 2 +-
gdb/syscalls/gdb-syscalls.dtd | 4 +-
gdb/testsuite/gdb.xml/bad-include.xml | 2 +-
gdb/testsuite/gdb.xml/core-only.xml | 2 +-
gdb/testsuite/gdb.xml/extra-regs.xml | 2 +-
gdb/testsuite/gdb.xml/inc-2.xml | 2 +-
gdb/testsuite/gdb.xml/includes.xml | 2 +-
gdb/testsuite/gdb.xml/loop.xml | 2 +-
83 files changed, 263 insertions(+), 84 deletions(-)
create mode 100755 gdb/contrib/xmllint.sh
base-commit: 63b85fe5d59d1eee20f177b4b6e653ddabdeebf7
--
2.51.0
next reply other threads:[~2026-08-26 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 21:22 Tom de Vries [this message]
2026-08-26 21:22 ` [PATCH v2 1/5] [pre-commit] Check xml files Tom de Vries
2026-08-26 21:22 ` [PATCH v2 2/5] [gdb] Fix xmllint namespace errors Tom de Vries
2026-08-26 21:22 ` [PATCH v2 3/5] [gdb] Fix target element validity error in features/gdb-target.dtd Tom de Vries
2026-08-26 21:22 ` [PATCH v2 4/5] [gdb] Fix syscalls-info -> syscalls_info in syscalls/gdb-syscalls.dtd Tom de Vries
2026-08-26 21:22 ` [PATCH v2 5/5] [pre-commit] Use --valid with xmllint Tom de Vries
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=20260826212209.925066-1-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
/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