[Bug breakpoints/20653] string_to_explicit_location has some weird code

cvs-commit at gcc dot gnu.org sourceware-bugzilla@sourceware.org
Wed Oct 5 16:32:00 GMT 2016


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

--- 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=e742d386c480efa5229bc8b1887a7718f840a457

commit e742d386c480efa5229bc8b1887a7718f840a457
Author: Tom Tromey <tom@tromey.com>
Date:   Fri Sep 30 15:43:40 2016 -0600

    PR gdb/20653 - small cleanup in string_to_explicit_location

    This bug points out that string_to_explicit_location compares a char*
    against '\0'; whereas comparing against NULL is more normal.

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

        PR breakpoints/20653:
        * location.c (string_to_explicit_location): Use NULL, not '\0'.

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


More information about the Gdb-prs mailing list