[Bug macros/29034] Can't print macros defined on the command-line with binaries built with clang

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

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Bruno Larsen <blarsen@sourceware.org>:

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

commit e7e7469e7a31bd5a406a03aa83a1cd648f5ef30d
Author: Bruno Larsen <blarsen@redhat.com>
Date:   Wed Apr 20 14:41:11 2022 -0300

    gdb: Fix issue with Clang CLI macros

    Clang up to version 15 (current) adds macros that were defined in the
    command line or by "other means", according to the Dwarf specification,
    after the last DW_MACRO_end_file, instead of before the first
    DW_MACRO_start_file, as the specification dictates.  When GDB reads the
    macros after the last file is closed, the macros never end up "in scope"
    and so we can't print them.  This has been submitted as a bug to Clang
    developers (https://github.com/llvm/llvm-project/issues/54506), and PR
    macros/29034 was opened for GDB to keep track of this.

    Seeing as there is no expected date for it to be fixed, add a workaround
    for all current versions of Clang.  The workaround detects when
    the main file would be closed and if the producer is Clang, and turns
    that operation into a noop, so we keep a reference to the current_file
    as those macros are read.

    A test case was added to confirm the functionality, and the KFAIL for
    running gdb.base/macro-source-path when using clang.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29034
    Approved-By: Simon Marchi <simon.marchi@efficios.com>

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