[v2,0/5] gdb: introduce limited array lengths while printing values

Message ID alpine.DEB.2.20.2211241944360.19931@tpp.orcam.me.uk
Headers
Series gdb: introduce limited array lengths while printing values |

Message

Maciej W. Rozycki Jan. 12, 2023, 9:01 a.m. UTC
  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