This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward
- From: "dmalcolm at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 29 Nov 2017 20:19:50 +0000
- Subject: [Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward
- Auto-submitted: auto-generated
- References: <bug-16874-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16874
--- Comment #16 from Dave Malcolm <dmalcolm at redhat dot com> ---
(In reply to Pedro Alves from comment #15)
> The series above is finally all merged to master. These are the related
> improvements that you'll find there:
[...]
Thanks for the improvements!
> * Breakpoints on C++ functions are now set on all scopes by default
>
> By default, breakpoints on functions/methods are now interpreted as
> specifying all functions with the given name ignoring missing
> leading scopes (namespaces and classes).
>
> For example, assuming a C++ program with symbols named:
>
> A::B::func()
> B::func()
>
> both commands "break func()" and "break B::func()" set a breakpoint
> on both symbols.
To clarify, if there is a symbol:
(anonymous namespace)::func()
will "break func" set a breakpoint on it? (without me having to type or
tab-complete the "(anonymous namespace)" part?)
[...]
--
You are receiving this mail because:
You are on the CC list for the bug.