From: Luis Machado <luis_gustavo@mentor.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC stub-side break conditions 2/5] Protocol changes
Date: Fri, 06 Jan 2012 22:39:00 -0000 [thread overview]
Message-ID: <4F0777F5.1000108@mentor.com> (raw)
In-Reply-To: <m3hb081qu6.fsf@fleche.redhat.com>
On 01/06/2012 07:08 PM, Tom Tromey wrote:
>>>>>> "Luis" == Luis Machado<luis_gustavo@mentor.com> writes:
> Luis> int
> Luis> +remote_supports_cond_breakpoints (void)
> Luis> +{
> Luis> + struct remote_state *rs = get_remote_state ();
> Luis> +
> Luis> + return rs->cond_breakpoints;
> Luis> +}
>
> I think this could be static.
>
True. Fixed.
Thanks!
--
Luis
lgustavo@codesourcery.com
prev parent reply other threads:[~2012-01-06 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 14:56 Luis Machado
2012-01-06 21:09 ` Tom Tromey
2012-01-06 22:39 ` Luis Machado [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=4F0777F5.1000108@mentor.com \
--to=luis_gustavo@mentor.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).