public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "drepper.fsp at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug macros/29725] Dwarf 5 C macros not handled
Date: Wed, 26 Oct 2022 22:09:37 +0000	[thread overview]
Message-ID: <bug-29725-4717-TTrtKHXhzy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29725-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Ulrich Drepper <drepper.fsp at gmail dot com> ---
Indeed, seems to work.

But the sequence is just part of the bigger code base.  Something like this is
used in gawk.  It seems the macro parser gets confused for larger code bases. 
The specific macro is used in a similar form in gawk (it's just a larger
structure/union).

This is the procedure to reproduce:

        cd /path/to/gawk/repo
        git pull
        echo debug > .developing
        ./bootstrap.sh && ./configure && make
        gdb ./gawk
        (gdb) break mk_binary
        (gdb) run -f test/divzero2.awk

Get to line 5539 and try to print ip2->memory->flags. I get:

        (gdb) p ip2->memory->flags
        There is no member named memory.

This is what I get even with the trunk gdb.

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

  parent reply	other threads:[~2022-10-26 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  9:59 [Bug macros/29725] New: " drepper.fsp at gmail dot com
2022-10-26 15:47 ` [Bug macros/29725] " simon.marchi at polymtl dot ca
2022-10-26 22:09 ` drepper.fsp at gmail dot com [this message]
2022-10-27  0:58 ` simark at simark dot ca
2022-10-27  1:21 ` 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-29725-4717-TTrtKHXhzy@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).