Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv3 0/3] Fixes and tests related to new boxed hint startup text
Date: Fri,  5 Dec 2025 19:53:14 +0000	[thread overview]
Message-ID: <cover.1764964133.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1764877518.git.aburgess@redhat.com>

Some fixes for the new boxed hint text.  But this grew slightly as one
of the issues is caused by a bug elsewhere in GDB.  And fixing that
exposed problem in a third area of GDB.  Sigh.

In v3:

  - Rewrote commit messages on first 2 patches.

  - Another minor tweak in patch #1, the debuginfod tests actually
    pass with this patch now.

  - Added a third patch, this adds a new switch to disable progress
    bars, which is then used by the debuginfod tests.

Thanks,
Andrew

---

Andrew Burgess (3):
  gdb: make get_chars_per_line return an unsigned value
  gdb: fix crashes and weird output from new boxed hint text
  WIP: disable progress bars setting

 gdb/NEWS                                      |   6 +
 gdb/cli-out.c                                 |  81 ++++++++--
 gdb/doc/gdb.texinfo                           |  15 ++
 gdb/main.c                                    |   5 +-
 gdb/testsuite/gdb.base/startup-hints.exp      | 144 ++++++++++++++++++
 .../build-id-no-debug-warning.exp             |   1 +
 .../gdb.debuginfod/corefile-mapped-file.exp   |   1 +
 gdb/testsuite/gdb.debuginfod/crc_mismatch.exp |   1 +
 .../gdb.debuginfod/fetch_src_and_symbols.exp  |   4 +
 .../gdb.debuginfod/solib-with-soname.exp      |   1 +
 gdb/top.c                                     |  23 ++-
 gdb/utils.c                                   |   3 +-
 gdb/utils.h                                   |   5 +-
 13 files changed, 268 insertions(+), 22 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/startup-hints.exp


base-commit: 36a4bbcec4b31ff7a5fb8e5a2e20acef9344c810
-- 
2.47.1


  parent reply	other threads:[~2025-12-05 19:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 16:38 [PATCH 0/4] " Andrew Burgess
2025-12-04 16:38 ` [PATCH 1/4] gdb: remove some unnecessary code from print_gdb_hints Andrew Burgess
2025-12-04 17:14   ` Patrick Monnerat
2025-12-04 16:38 ` [PATCH 2/4] gdb: small white space fix in print_gdb_hints Andrew Burgess
2025-12-04 16:38 ` [PATCH 3/4] gdb: make get_chars_per_line return an unsigned value Andrew Burgess
2025-12-04 16:38 ` [PATCH 4/4] gdb: fix crashes and weird output from new boxed hint text Andrew Burgess
2025-12-04 19:02 ` [PATCH 0/4] Fixes and tests related to new boxed hint startup text Guinevere Larsen
2025-12-04 19:32   ` Andrew Burgess
2025-12-04 19:47 ` [PATCH 0/2] " Andrew Burgess
2025-12-04 19:47   ` [PATCH 1/2] gdb: make get_chars_per_line return an unsigned value Andrew Burgess
2025-12-04 19:47   ` [PATCH 2/2] gdb: fix crashes and weird output from new boxed hint text Andrew Burgess
2025-12-05  7:06     ` Eli Zaretskii
2025-12-05 10:17       ` Andrew Burgess
2025-12-05 11:19         ` Eli Zaretskii
2025-12-05 19:53   ` Andrew Burgess [this message]
2025-12-05 19:53     ` [PATCHv3 1/3] gdb: make get_chars_per_line return an unsigned value Andrew Burgess
2025-12-10 16:48       ` Tom Tromey
2025-12-05 19:53     ` [PATCHv3 2/3] gdb: fix crashes and weird output from new boxed hint text Andrew Burgess
2025-12-10 16:51       ` Tom Tromey
2025-12-05 19:53     ` [PATCHv3 3/3] WIP: disable progress bars setting Andrew Burgess
2025-12-06  9:12       ` Eli Zaretskii
2025-12-09 17:32       ` Andrew Burgess
2025-12-10 16:55         ` Tom Tromey
2025-12-15 15:33           ` Andrew Burgess
2025-12-16  7:40       ` Tom de Vries
2025-12-16 10:05         ` Andrew Burgess

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=cover.1764964133.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --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