[Bug python/17981] gdb.breakpoints() returns None if there are no breakpoints; should return empty sequence

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17981

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1957f6b89f3db02d51e3e3361de6af073a03f19d

commit 1957f6b89f3db02d51e3e3361de6af073a03f19d
Author: Tom Tromey <tom@tromey.com>
Date:   Wed May 18 21:41:28 2016 -0600

    Fix PR python/17981

    PR python/17981 notes that gdb.breakpoints() returns None when there
    are no breakpoints; whereas an empty list or tuple would be more in
    keeping with Python and the documentation.

    This patch fixes the bug by changing the no-breakpoint return to make
    an empty tuple.

    Built and regtested on x86-64 Fedora 23.

    2016-05-23  Tom Tromey  <tom@tromey.com>

        PR python/17981:
        * python/py-breakpoint.c (gdbpy_breakpoints): Return a new tuple
        when there are no breakpoints.

    2016-05-23  Tom Tromey  <tom@tromey.com>

        * python.texi (Basic Python): Document gdb.breakpoints return.

    2016-05-23  Tom Tromey  <tom@tromey.com>

        PR python/17981:
        * gdb.python/py-breakpoint.exp (test_bkpt_basic): Add test for
        no-breakpoint case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.