public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug macros/29034] Can't print macros defined on the command-line with binaries built with clang
Date: Thu, 16 May 2024 10:29:12 +0000	[thread overview]
Message-ID: <bug-29034-4717-63qnZUfrbA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29034-4717@http.sourceware.org/bugzilla/>

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vries at gcc dot gnu.org

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Andrew Burgess from comment #3)
> Given we now have a work around for this issue in GDB, could we close this
> bug?

AFAIU, what remains to be done is to wait for lldb to fix this issue, and to
limit the workaround to the broken versions.

I'm not sure if that is enough reason to keep this PR open.

The issue is already documented in the code like this:
...
              /* Clang, until the current version, misplaces some macro         
                 definitions - such as ones defined in the command line,        
                 putting them after the last DW_MACRO_end_file instead of       
                 before the first DW_MACRO_start_file.  Since at the time       
                 of writing there is no clang version with this bug fixed,      
                 we check for any clang producer.  This should be changed       
                 to producer_is_clang_lt_XX when possible. */
...

I propose to close the PR.  If we really want a PR open for this, we could file
a spin-off one, with for instance a tag in the subject "blocked on llvm" or
some such.

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

      parent reply	other threads:[~2024-05-16 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  0:54 [Bug gdb/29034] New: " simark at simark dot ca
2022-04-08  0:01 ` [Bug macros/29034] " tromey at sourceware dot org
2022-04-08  0:07 ` tromey at sourceware dot org
2022-04-18 19:17 ` blarsen at redhat dot com
2022-11-03 13:14 ` cvs-commit at gcc dot gnu.org
2024-01-19 13:20 ` aburgess at redhat dot com
2024-05-16 10:29 ` vries at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29034-4717-63qnZUfrbA@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).