public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27966] macro tests failing when using -gdwarf-5 -gsplit-dwarf
Date: Wed, 04 Jan 2023 17:23:33 +0000 [thread overview]
Message-ID: <bug-27966-4717-JAEMoHA0gI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27966-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27966
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
(In reply to Sourabh Singh Tomar from comment #0)
> **NOTE**:
> *Non-absolute/Relative* path still does not work(both split & no-split case)
> yet :(
> Patch in progress, needs clarification on the approach from maintainers.
> https://sourceware.org/pipermail/gdb-patches/2021-May/179190.html
>
> i.e
> ```
> $ clang -fdebug-macro -gdwarf-5 -gsplit-dwarf macro.c
> gdb a.out -q
> Reading symbols from a.out...
> (gdb) start
> Temporary breakpoint 1 at 0x201664: file macro.c, line 2.
> Starting program: /home/sourabh/work/dwarf/c_c++/a.out
>
> Temporary breakpoint 1, main () at macro.c:2
> 2 int main() {}
> (gdb) info macros
> ```
This should be fixed since this commit
https://gitlab.com/gnutools/binutils-gdb/-/commit/7900b17e334b114ff149c5a3da7884e6ab3f7136
Can you confirm?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-04 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 7:24 [Bug gdb/27966] New: " sourav0311 at gmail dot com
2021-06-08 7:25 ` [Bug gdb/27966] " sourav0311 at gmail dot com
2023-01-04 1:44 ` tromey at sourceware dot org
2023-01-04 17:23 ` simark at simark dot ca [this message]
2023-01-04 22:37 ` tromey at sourceware dot org
2023-01-05 1:42 ` simark at simark dot ca
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-27966-4717-JAEMoHA0gI@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).