#1 kdbg hangs on breakpoint-entry via keyboard

[Michal Weis]

if you have two functions with same name, and typing breakpoint manually e.g. myclass::func, and there are two functions: myclass:func(int) and myclass::func(char *, float), gdb displays 'interactive' selection which
function do you want to break:
(gdb) b dbtoc::finddbf
[0] cancel
[1] all
[2] dbtoc::finddbf(dbfile_entry *) at dbtoc.cc:899
[3] dbtoc::finddbf(long) at dbtoc.cc:960
>
and waits for users answer... and kdbg waits forever as well....

ps: for resolving breakpoints interactively, a good hint is to use <TAB>, which in gdb lists symbols starting with that pharse given by you... some LIST buttom in kdbg to use this feature would be good also...

[Johannes Sixt]

This problem is known to me.
It is not easy to fix it, so it will have to wait.
Sorry.

A work-around is to select Execution->Break.
This will "wake up" kdbg.