From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Re: bug in mi when setting breakpoint
Date: Thu, 17 Jan 2008 20:35:00 -0000 [thread overview]
Message-ID: <18319.48140.659381.847861@kahikatea.snap.net.nz> (raw)
In-Reply-To: <fmnogj$pat$1@ger.gmane.org>
> This is different to what I've proposed -- namely reporting "there are
> several overloaded functions" and then allowing the frontend to select a
> specific one.
I must have missed that. Can you please point to a reference?
> The solution you propose does not give a frontend a way to
> control which overloaded function to set breakpoint on, which seems like an
> important limitation for me.
After selecting all breakpoints GDB prints:
warning: Multiple breakpoints were set.
Use the "delete" command to delete unwanted breakpoints.
I can see it may be an inconvenience but not how it can be a limitation.
IMHO, it seems preferable to generating prompts that are not compatible with
rules for MI output.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-01-17 20:35 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 [this message]
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
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=18319.48140.659381.847861@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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