public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nilsgladitz at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/27556] "<no data fields>" for some C++ coroutine frame types
Date: Sat, 13 Mar 2021 09:42:19 +0000	[thread overview]
Message-ID: <bug-27556-4717-bkccfV6Tii@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27556-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Nils Gladitz <nilsgladitz at gmail dot com> ---
Thank you for looking into this.

I am not familiar enough with the corresponding standards to tell if nesting
the type definition inside the function is a violation or valid but unusual.

FWIW I think the type is tightly coupled with the coroutine so nesting it in
the corresponding function might make sense that way. I don't know if there is
precedence for this elsewhere but given that the implementation is new that
might justify the current uncommonness.

In the working case of "function1" the type is also nested and the function
also artificial but it is not marked as a declaration which if I understand you
correctly might be why it currently breaks for "function2".

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

  parent reply	other threads:[~2021-03-13  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 12:00 [Bug c++/27556] New: " nilsgladitz at gmail dot com
2021-03-10 12:01 ` [Bug c++/27556] " nilsgladitz at gmail dot com
2021-03-12 19:16 ` tromey at sourceware dot org
2021-03-13  9:42 ` nilsgladitz at gmail dot com [this message]
2021-03-16 13:11 ` nilsgladitz at gmail dot com
2021-03-31 19:45 ` tromey at sourceware dot org

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-27556-4717-bkccfV6Tii@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).