[PATCH] Re: bug in mi when setting breakpoint

Daniel Jacobowitz drow@false.org
Tue Jan 29 20:15:00 GMT 2008


On Mon, Jan 21, 2008 at 10:28:06AM +0300, Vladimir Prus wrote:
> As I've mentioned, in non-stop mode, adding all breakpoint and then removing
> undesired ones won't work.

I don't think this is right.  "break f" -> [f(int), f(long)] is exactly
the same as "break f" -> [f<int>(), f<long>()] or "break f" ->
[f inlined into g, f inlined into h].  The fact that we handle all
these things differently in GDB today seems like a bug to me.

If the IDE wants to set a breakpoint on one of a group of overloaded
functions, where it only knows the name, can't it query GDB for the
list separately from -break-insert?

We have got a problem today: we print out prompts for GDB/MI clients
in a completely invalid way.  Let's figure out what those prompts
should do in MI mode, and make them do it instead of prompting.

-- 
Daniel Jacobowitz
CodeSourcery



More information about the Gdb-patches mailing list