aboutsummaryrefslogtreecommitdiff
path: root/bfd/cpu-cr16.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2021-07-13 21:07:32 -0400
committerSimon Marchi <simon.marchi@polymtl.ca>2021-07-23 15:38:54 -0400
commit3e1e8561c387dbe2dbb93d52fbd27ebcb0b7f3a1 (patch)
tree1a3b4c168febb86029497af34429340c7f37f59c /bfd/cpu-cr16.c
parent5538b03c98e77756b1e1d3e3be86f997a78e6d11 (diff)
downloadgdb-3e1e8561c387dbe2dbb93d52fbd27ebcb0b7f3a1.zip
gdb-3e1e8561c387dbe2dbb93d52fbd27ebcb0b7f3a1.tar.gz
gdb-3e1e8561c387dbe2dbb93d52fbd27ebcb0b7f3a1.tar.bz2
gdb/testsuite: test get/set value of unregistered Guile parameter
When creating a parameter in Guile, you have to create it using make-parameter and then register it with GDB with register-parameter!. In between, it's still possible (though not documented) to set the parameter's value. I broke this use case by mistake while writing this series, so thought it would be good to have a test for it. I suppose that people could use this "feature" to give their parameter an initial value, even though make-parameter has an initial-value parameter for this. Nevertheless, changing this behavior could break some scripts, which is why I think it's important for it to be tested. Change-Id: I5b2103e3cec0cfdcccf7ffb00eb05fed8626e66d
Diffstat (limited to 'bfd/cpu-cr16.c')
0 files changed, 0 insertions, 0 deletions