From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/5] Return error code in get_number
Date: Mon, 17 Mar 2014 00:51:00 -0000 [thread overview]
Message-ID: <53264680.9090704@codesourcery.com> (raw)
In-Reply-To: <87lhwckfq8.fsf@fleche.redhat.com>
On 03/14/2014 10:38 PM, Tom Tromey wrote:
> It seems to me that an MI client already knows all the breakpoint
> numbers. I'm having trouble picturing the scenario where I'd want my MI
> client to use a convenience variable instead.
This facilitates writing MI test cases that we don't have to hard-code
breakpoint numbers anymore. Keith pointed this out in the review
https://sourceware.org/ml/gdb-patches/2014-01/msg00824.html and I think
that is good to have, so I write this patch series. Can this justify
the changes in this series?
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-03-17 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 2:35 Yao Qi
2014-03-13 2:35 ` [PATCH 4/5] get_number returns status in details Yao Qi
2014-03-13 2:35 ` [PATCH 2/5] Change argument 'args' of get_tracepoint_by_number to char * Yao Qi
2014-03-13 2:35 ` [PATCH 5/5] Accept convenience variable in commands -break-passcount and -break-commands Yao Qi
2014-03-14 8:22 ` Eli Zaretskii
2014-03-13 2:35 ` [PATCH 3/5] Emit wrong value error when parsing range Yao Qi
2014-03-13 2:35 ` [PATCH 1/5] Remove argument 'state' from get_tracepoint_by_number Yao Qi
2014-03-13 15:14 ` [PATCH 0/5] Return error code in get_number Tom Tromey
2014-03-14 0:59 ` Yao Qi
2014-03-14 14:38 ` Tom Tromey
2014-03-17 0:51 ` Yao Qi [this message]
2014-05-15 17:58 ` Tom Tromey
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=53264680.9090704@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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