public inbox for
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <>
Cc: Andrew Burgess <>, Tom Tromey <>,
	 Richard Bunt <>
Subject: [PATCH v4 0/6] gdb: introduce limited array lengths while printing values
Date: Fri, 10 Feb 2023 14:18:54 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)


 This is v4 of the patch series, addressing the suggestion made by Tom 
Tromey for v3 as to avoiding the use of explicit ranges for out-of-bounds 
accesses to value history entries.  There's now an extra clean-up WRT the 
use of standard C++ <climits> macros too.  The remaining changes have been 
adjusted as requested and I will commit them where approved along with the 
outstanding ones.

 See individual change descriptions for details.

 I have regression-tested it natively with a `x86_64-linux-gnu' system.  
OK to apply?


             reply	other threads:[~2023-02-10 14:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 14:18 Maciej W. Rozycki [this message]
2023-02-10 14:19 ` [PATCH v4 1/6] GDB: Switch to using C++ standard integer type limits Maciej W. Rozycki
2023-02-10 21:13   ` Tom Tromey
2023-02-10 14:19 ` [PATCH v4 2/6] GDB: Ignore `max-value-size' setting with value history accesses Maciej W. Rozycki
2023-02-10 14:19 ` [PATCH v4 3/6] GDB: Fix the mess with value byte/bit range types Maciej W. Rozycki
2023-02-10 14:19 ` [PATCH v4 4/6] GDB: Only make data actually retrieved into value history available Maciej W. Rozycki
2023-02-10 21:16   ` Tom Tromey
2023-02-10 14:19 ` [PATCH v4 5/6] GDB/testsuite: Add `-nonl' option to `gdb_test' Maciej W. Rozycki
2023-02-10 14:19 ` [PATCH v4 6/6] GDB: Introduce limited array lengths while printing values Maciej W. Rozycki
2023-02-13 14:45   ` Simon Marchi
2023-02-14 19:20     ` Maciej W. Rozycki
2023-02-23 21:16       ` Maciej W. Rozycki
2023-02-10 21:17 ` [PATCH v4 0/6] gdb: introduce " Tom Tromey
2023-02-10 23:50   ` Maciej W. Rozycki

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).