Feature wanted: Handle "Ambiguous symbol error" with more comfort

[bw-86]

When I am trying to set a breakpoint at a line by clicking on it, as I would do in Visual Studio, it sometimes fails with output like this:

Matched: my_module!MyType::member_function+0x5df (00fd2c8f)
Matched: my_module!MyType::member_function+0x610 (00fd2cc0)
Ambiguous symbol error at '`my_module!F:\src\somefile.cpp:411+`)'

I understand that the debugger does not know which breakpoint I want to set. Most of the time, I also do not know which of these I actually want. I therefore end up having to simply set both.

I feel that the debugger does not support me as much as it could here. A dynamic link "Set breakpoints at all matched addresses" would help tremendously here. An option "Set all breakpoints on ambiguous symbol errors" would be even better. As a more minor improvement, at least each "Matched:" line could include a clickable link to "Set breakpoint".