Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] [gdb/testsuite] Two fixes in gdb.python/py-section-script.exp
Date: Tue, 28 Jul 2026 18:00:14 +0200	[thread overview]
Message-ID: <20260728160016.3087552-1-tdevries@suse.de> (raw)

The first patch fixes problems found with make-check-all.sh.

The second patch fixes a problem when using an older objdump that doesn't
suppport --decompress.

Tom de Vries (2):
  [gdb/testsuite] Fix gdb.python/py-section-script.exp with
    make-check-all.sh
  [gdb/testsuite] Fix gdb.python/py-section-script.exp with older
    objdump

 .../gdb.python/py-section-script.exp          | 59 +++++++++++--------
 1 file changed, 35 insertions(+), 24 deletions(-)


base-commit: cd02e2a209482dd9fa06945ffec0675da7dfd74e
-- 
2.51.0


             reply	other threads:[~2026-07-28 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 16:00 Tom de Vries [this message]
2026-07-28 16:00 ` [PATCH 1/2] [gdb/testsuite] Fix gdb.python/py-section-script.exp with make-check-all.sh Tom de Vries
2026-07-28 16:00 ` [PATCH 2/2] [gdb/testsuite] Fix gdb.python/py-section-script.exp with older objdump 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=20260728160016.3087552-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