This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/16874] Setting a breakpoint on function in anonymous namespace is unnecessarily awkward


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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]