diff options
author | Jason Molenda <jmolenda@apple.com> | 2024-09-03 16:45:28 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-09-03 16:45:28 -0700 |
commit | b076f6640e3c2781410588f4a8e4ccfeed8eb606 (patch) | |
tree | f1d3b1ff691932fd60f4f4b4cd46d81e73eb4abc /llvm/lib/Transforms/Utils/LoopUtils.cpp | |
parent | 18263c319092b878f25dd4025830f8e6691245d4 (diff) | |
download | llvm-b076f6640e3c2781410588f4a8e4ccfeed8eb606.zip llvm-b076f6640e3c2781410588f4a8e4ccfeed8eb606.tar.gz llvm-b076f6640e3c2781410588f4a8e4ccfeed8eb606.tar.bz2 |
[lldb] Remove limit on max memory read size (#105765)
`memory read` will return an error if you try to read more than 1k bytes
in a single command, instructing you to set
`target.max-memory-read-size` or use `--force` if you intended to read
more than that. This is a safeguard for a command where people are being
explicit about how much memory they would like lldb to read (either to
display, or save to a file) and is an annoyance every time you need to
read more than a small amount. If someone confuses the --count argument
with the start address, lldb may begin dumping gigabytes of data but I'd
rather that behavior than requiring everyone to special-case their way
around a common use case.
I don't want to remove the setting because many people have added (much
larger) default max read sizes to their ~/.lldbinit files after hitting
this behavior. Another option would be to stop reading/using the value
in Target.cpp, but I see no harm in leaving the setting if someone
really does prefer to have a small cap on their memory read size.
Diffstat (limited to 'llvm/lib/Transforms/Utils/LoopUtils.cpp')
0 files changed, 0 insertions, 0 deletions