aboutsummaryrefslogtreecommitdiff
path: root/depcomp
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-06-01 11:54:17 -0600
committerTom Tromey <tromey@adacore.com>2023-06-22 09:46:24 -0600
commitd8a001f57016eff05977e9699c7aabdf4302c71b (patch)
tree8f52cf811c7b40b9168be6bd7f51e9dfa9e418fc /depcomp
parent0aafd5d038581b1eaf7f37b185f9d2c9be47386d (diff)
downloadbinutils-d8a001f57016eff05977e9699c7aabdf4302c71b.zip
binutils-d8a001f57016eff05977e9699c7aabdf4302c71b.tar.gz
binutils-d8a001f57016eff05977e9699c7aabdf4302c71b.tar.bz2
Implement DAP "hover" context
A DAP client can request that an expression be evaluated in "hover" context, meaning that it should not cause side effects. In gdb, this can be implemented by temporarily setting a few "may-" parameters to "off". In order to make this work, I had to also change "may-write-registers" so that it can be changed while the program is running. I don't think there was any reason for this prohibition in the first place. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30476
Diffstat (limited to 'depcomp')
0 files changed, 0 insertions, 0 deletions