diff options
author | Andrew Burgess <aburgess@redhat.com> | 2023-12-13 09:44:33 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2024-03-31 11:13:09 +0100 |
commit | 437d237a547def823434dd656e5c138a2263dd5c (patch) | |
tree | 51dd67a065654d179d59db406c445ae47cbbb2c6 /gdb/python/py-lazy-string.c | |
parent | 3d42db971fc7cb0a5fe9b4526b12539019b5c27e (diff) | |
download | binutils-437d237a547def823434dd656e5c138a2263dd5c.zip binutils-437d237a547def823434dd656e5c138a2263dd5c.tar.gz binutils-437d237a547def823434dd656e5c138a2263dd5c.tar.bz2 |
gdb: the extra_string in a dprintf breakpoint is never nullptr
Given the changes in the previous couple of commits, this commit
cleans up some of the asserts and 'if' checks related to the
extra_string within a dprintf breakpoint.
This commit:
1. Adds some asserts to update_dprintf_command_list about the
breakpoint type, and that the extra_string is not nullptr,
2. Given that we know extra_string is not nullptr (this is enforced
when the breakpoint is created), we can simplify
code_breakpoint::code_breakpoint -- it no longer needs to check for
the extra_string is nullptr case,
3. In dprintf_breakpoint::re_set we can remove the assert (this will
be checked within update_dprintf_command_list, we can also remove
the redundant 'if' check.
There should be no user visible changes after this commit.
Diffstat (limited to 'gdb/python/py-lazy-string.c')
0 files changed, 0 insertions, 0 deletions