public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jengelh at inai dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30209] New: Inconsistency between lambdas' signatures and that of the function they are in
Date: Tue, 07 Mar 2023 15:47:10 +0000	[thread overview]
Message-ID: <bug-30209-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30209
           Summary: Inconsistency between lambdas' signatures and that of
                    the function they are in
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: jengelh at inai dot de
  Target Milestone: ---

Moved from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109020

== Input ==

$ cat x.cpp
#include <stdint.h>
static void ff(uint64_t b) { [&](){}(); }
int main() { ff(0); }
$ nm -C a.out | grep ff
0000000000401121 t ff(unsigned long)
0000000000401116 t ff(unsigned long)::{lambda()#1}::operator()() const
$ g++ x.cpp -g
$ gdb a.out
(gdb) b ff<TAB><TAB>

== Observed ==

Tab completion yields:

ff(uint64_t)
ff(unsigned long)::{lambda()#1}::operator()() const

== Expectation ==

ff(unsigned long)
ff(unsigned long)::{lambda()#1}::operator()() const

[or]

ff(uint64_t)
ff(uint64_t)::{lambda()#1}::operator()() const

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

                 reply	other threads:[~2023-03-07 15:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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