diff options
| author | Tom Tromey <tromey@adacore.com> | 2023-10-04 12:58:32 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-10-16 09:27:28 -0600 |
| commit | 138c7d2661044d80dddc0445616aada039af1a95 (patch) | |
| tree | 181bb22124066287be3b60f4047f7c1e7c335b48 /gdb/exec.c | |
| parent | fd00374fc73e990b2a1b97a1bab431e0466f5efc (diff) | |
| download | gdb-138c7d2661044d80dddc0445616aada039af1a95.zip gdb-138c7d2661044d80dddc0445616aada039af1a95.tar.gz gdb-138c7d2661044d80dddc0445616aada039af1a95.tar.bz2 | |
Fix register-setting response from DAP
Andry noticed that given a DAP setExpression request, where the
expression to set is a register, DAP will return the wrong value -- it
will return the old value, not the updated one.
This happens because gdb.Value.assign (which was recently added for
DAP) does not update the value.
In this patch, I chose to have the assign method update the Value
in-place. It's also possible to have it return a new value, but this
didn't seem very useful to me.
Diffstat (limited to 'gdb/exec.c')
0 files changed, 0 insertions, 0 deletions