use explicit returns to avoid checker confusion
The checker does not understand the idiom if (except.reason < 0) { do_cleanups (whatever); GDB_PY_HANDLE_EXCEPTION (except); } because it doesn't realize that the nested 'if' actually has the same condition. This fixes instances of this to be more explicit. * python/py-breakpoint.c (bppy_get_commands): Use explicit, unconditional return. * python/py-frame.c (frapy_read_var): Likewise. * python/python.c (gdbpy_decode_line): Likewise.
This commit is contained in:
parent
c27e16e3f1
commit
f330038710
4 changed files with 13 additions and 3 deletions
|
@ -492,7 +492,8 @@ bppy_get_commands (PyObject *self, void *closure)
|
|||
if (except.reason < 0)
|
||||
{
|
||||
do_cleanups (chain);
|
||||
GDB_PY_HANDLE_EXCEPTION (except);
|
||||
gdbpy_convert_exception (except);
|
||||
return NULL;
|
||||
}
|
||||
|
||||
cmdstr = ui_file_xstrdup (string_file, &length);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue