[Bug breakpoints/23210] [8.1/8.2 Regression] Bogus Breakpoint address adjusted from 0xf7fe7dd3 to 0xfffffffff7fe7dd3.

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

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

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Omair Javaid <omjavaid@sourceware.org>:

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

commit 5969f0dba74e17c694faf333b120f1e0b95783ed
Author: Omair Javaid <omair.javaid@linaro.org>
Date:   Sat May 26 05:58:51 2018 +0500

    Unset gdbarch significant_addr_bit by default

    This patch fixes a bug introduced by fix to AArch64 pointer tagging.

    In our fix for tagged pointer support our agreed approach was to sign
    extend user-space address after clearing tag bits. This is not same
    for all architectures and this patch allows sign extension for
    addresses on targets which specifically set significant_addr_bit.

    More information about patch that caused the issues and discussion
    around tagged pointer support can be found in links below:

    https://sourceware.org/ml/gdb-patches/2018-05/msg00000.html
    https://sourceware.org/ml/gdb-patches/2017-12/msg00159.html

    gdb/ChangeLog:

    2018-05-31  Omair Javaid  <omair.javaid@linaro.org>

        PR gdb/23210
        * gdbarch.sh (significant_addr_bit): Default to zero when
        not set by target architecture.
        * gdbarch.c: Re-generated.
        * utils.c (address_significant): Update.

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