public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
	 Richard Bunt <Richard.Bunt@arm.com>
Subject: [PATCH v2 0/5] gdb: introduce limited array lengths while printing values
Date: Thu, 12 Jan 2023 09:01:28 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.20.2211241944360.19931@tpp.orcam.me.uk> (raw)

Hi,

 This is v2 of Andrew's RFC, originally posted here: 
<https://sourceware.org/pipermail/gdb-patches/2021-October/182435.html>.

 Following Tom's feedback I have updated the original change so that data 
up to `max-value-size' is retrieved and stored in the history regardless 
of how much less has been requested with the relevant `print' command.  

 This has revealed issues with value history handling where entries were 
not retrieved due to `max-value-size' setting where accessing the original 
data object would work, and then where out of range accesses pretended to 
retrieve data or returned memory faults.

 I have updated the change to make the `output' command follow the same 
rules (except for storing the value retrieved in the value history of 
course).  This in turn required a test framework update as it seems the 
only command that does not produce a new line character/sequence between 
data output and the following command prompt; this has also revealed this 
command had no testsuite coverage at all until now.

 Consequently this has now become a patch series addressing each of these 
issues individually.  See individual change descriptions (and any extra 
discussion) for details.

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

  Maciej

             reply	other threads:[~2023-01-12  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  9:01 Maciej W. Rozycki [this message]
2023-01-12  9:01 ` [PATCH v2 1/5] GDB: Ignore `max-value-size' setting with value history accesses Maciej W. Rozycki
2023-01-13 16:18   ` Andrew Burgess
2023-01-20 13:41     ` Maciej W. Rozycki
2023-01-12  9:01 ` [PATCH v2 2/5] GDB: Fix the mess with value byte/bit range types Maciej W. Rozycki
2023-01-12  9:02 ` [PATCH v2 3/5] GDB: Only make data actually retrieved into value history available Maciej W. Rozycki
2023-01-12  9:02 ` [PATCH v2 4/5] GDB/testsuite: Add `-nonl' option to `gdb_test' Maciej W. Rozycki
2023-01-12  9:02 ` [PATCH v2 5/5] GDB: Introduce limited array lengths while printing values Maciej W. Rozycki
2023-01-12 10:04   ` Eli Zaretskii
2023-01-12 10:58     ` 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:
  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=alpine.DEB.2.20.2211241944360.19931@tpp.orcam.me.uk \
    --to=macro@embecosm.com \
    --cc=Richard.Bunt@arm.com \
    --cc=aburgess@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).