From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Re: bug in mi when setting breakpoint
Date: Tue, 29 Jan 2008 20:15:00 -0000 [thread overview]
Message-ID: <20080129200724.GF9019@caradoc.them.org> (raw)
In-Reply-To: <200801211028.07452.ghost@cs.msu.su>
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
prev parent reply other threads:[~2008-01-29 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071216125625.GE4783@coin>
[not found] ` <18277.36237.521792.245470@kahikatea.snap.net.nz>
[not found] ` <18316.10856.89097.335103@kahikatea.snap.net.nz>
2008-01-16 22:37 ` Nick Roberts
2008-01-17 14:26 ` Vladimir Prus
2008-01-17 20:35 ` Nick Roberts
2008-01-19 11:52 ` Vladimir Prus
2008-01-19 21:45 ` Nick Roberts
2008-01-20 10:08 ` Vladimir Prus
2008-01-20 10:38 ` Nick Roberts
2008-01-20 11:09 ` Vladimir Prus
2008-01-20 20:32 ` Nick Roberts
2008-01-21 7:28 ` Vladimir Prus
2008-01-21 8:41 ` Nick Roberts
2008-01-29 20:15 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080129200724.GF9019@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox