diff options
| author | Tom Tromey <tom@tromey.com> | 2018-09-18 06:27:09 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2018-10-06 22:17:45 -0600 |
| commit | 2a8be20359dba9cc684fd3ffa222d985399f3b18 (patch) | |
| tree | cfd6e84fca0e481698a7f8ab984ae48beaac7b89 /gdb/lm32-tdep.c | |
| parent | 2fb009bbd1d65a837e5032e744ba30b49c7f472a (diff) | |
| download | gdb-2a8be20359dba9cc684fd3ffa222d985399f3b18.zip gdb-2a8be20359dba9cc684fd3ffa222d985399f3b18.tar.gz gdb-2a8be20359dba9cc684fd3ffa222d985399f3b18.tar.bz2 | |
Fix Python gdb.Breakpoint.location crash
I noticed today that gdb.Breakpoint.location will crash when applied
to a catchpoint made with "catch throw".
The bug is that "catch throw" makes a breakpoint that is of type
bp_breakpoint, but which does not have a location.
Regression tested on x86-64 Fedora 28.
gdb/ChangeLog
2018-10-06 Tom Tromey <tom@tromey.com>
* python/py-breakpoint.c (bppy_get_location): Handle a
bp_breakpoint without a location.
gdb/testsuite/ChangeLog
2018-10-06 Tom Tromey <tom@tromey.com>
* gdb.python/py-breakpoint.exp (check_last_event): Check location
of a "throw" catchpoint.
Diffstat (limited to 'gdb/lm32-tdep.c')
0 files changed, 0 insertions, 0 deletions