public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/13383] scope for top-level using statements is wrong
Date: Sun, 17 Dec 2023 14:12:29 +0000	[thread overview]
Message-ID: <bug-13383-4717-ldep8kTB1B@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13383-4717@http.sourceware.org/bugzilla/>

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

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org
   Target Milestone|---                         |14.1
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #1 from Hannes Domani <ssbssa at sourceware dot org> ---
This is working since gdb-14.1, I think it was fixed by this commit:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=68ce1575fc902958a9b1d197e2c79ea842a7776d

Now you get:
```
Breakpoint 1, xfun () at gdb-13383.cpp:16
16        return Q::C::x;               // Breakpoint xfun
                       ^
(gdb) p x
No symbol "x" in current context.
(gdb) c
Continuing.

Breakpoint 2, yfun () at gdb-13383.cpp:22
22        return x;                     // Breakpoint yfun
                 ^
(gdb) p x
$1 = 5
```

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

      reply	other threads:[~2023-12-17 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 16:59 [Bug c++/13383] New: " tromey at redhat dot com
2023-12-17 14:12 ` ssbssa at sourceware dot 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-13383-4717-ldep8kTB1B@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).