diff options
| author | Tom Tromey <tom@tromey.com> | 2016-05-19 15:52:52 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2016-07-13 13:20:59 -0600 |
| commit | 43684a7b844bce64735940b55b667f7086fa3d44 (patch) | |
| tree | 25390da3dd7000fc5254800f61c4b467fedf1a1c /gdb/testsuite | |
| parent | cda75e7050781403875413a57c5700e67b1c6269 (diff) | |
| download | gdb-43684a7b844bce64735940b55b667f7086fa3d44.zip gdb-43684a7b844bce64735940b55b667f7086fa3d44.tar.gz gdb-43684a7b844bce64735940b55b667f7086fa3d44.tar.bz2 | |
use user_breakpoint_p in python code
I noticed that bppy_get_visibility and gdbpy_breakpoint_created
implemented their own visibility checks, but subtly different from
user_breakpoint_p. I think the latter is more correct, and so changed
the Python code to use it.
I suspect there isn't a decent way to test this, so no new test.
Built and regtested on x86-64 Fedora 23.
2016-07-13 Tom Tromey <tom@tromey.com>
* python/py-breakpoint.c (bppy_get_visibility)
(gdbpy_breakpoint_created): Use user_breakpoint_p.
Diffstat (limited to 'gdb/testsuite')
0 files changed, 0 insertions, 0 deletions