aboutsummaryrefslogtreecommitdiff
path: root/gdb/tui/ChangeLog
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2025-01-04 12:10:42 +0100
committerTom de Vries <tdevries@suse.de>2025-01-04 12:10:42 +0100
commitdeea250ab63d84a58125ca0963c625b50468a578 (patch)
tree4b8d6ede1dcfe638a5154bb71799d9b9b2c4d721 /gdb/tui/ChangeLog
parent09859118ffc86b311d47aa461f722a720045e049 (diff)
downloadgdb-master.zip
gdb-master.tar.gz
gdb-master.tar.bz2
[gdb/testsuite] Add gdb.python/py-commands-breakpoint.expHEADmaster
A recent discussion about what commands are allowed during gdb.Breakpoint.stop, made me wonder if there would be less restrictions if we'd do those commands as part of a breakpoint command list instead. Attribute gdb.Breakpoint.commands is a string with gdb commands, so I tried implementing a new class PyCommandsBreakpoint, derived from gdb.Breakpoint, that supports a py_commands method. My original idea was to forbid setting PyCommandsBreakpoint.commands, and do: ... def py_commands(self): print("VAR: %d" % self.var) self.var += 1 gdb.execute("continue") ... but as it turns out 'gdb.execute("continue")' does not behave the same way as continue. I've filed PR python/32454 about this. So the unsatisfactory solution is to first execute PyCommandsBreakpoint.py_commands: ... def py_commands(self): print("VAR: %d" % self.var) self.var += 1 ... and then: ... self.commands = "continue" ... I was hoping for a better outcome, but having done the work of writing this, I suppose it has use as a test-case, perhaps also as an example of how to work around PR python/32454. Tested on x86_64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32454
Diffstat (limited to 'gdb/tui/ChangeLog')
0 files changed, 0 insertions, 0 deletions