From: dje@google.com
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/4] de-couple %Stop from notification: gdb
Date: Fri, 24 Aug 2012 19:00:00 -0000 [thread overview]
Message-ID: <20535.53033.569482.293453@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <1345775139-13576-3-git-send-email-yao@codesourcery.com>
Yao Qi writes:
> This patch is to de-couple vStopped/%Stop from notification in gdb side.
Hi. Just a few nits, maybe more to follow.
> gdb:
>
> 2012-08-24 Yao Qi <yao@codesourcery.com>
>
> (struct remote_state): Move to remote.h.
What's the reason for moving struct remote_state to remote.h?
[I did a simple grep and couldn't find a reason, I could have missing something of course.]
Having it live in remote.c means the implementation is "private" to just that file.
> diff --git a/gdb/remote-notif.c b/gdb/remote-notif.c
> new file mode 100644
> index 0000000..ca7f821
> --- /dev/null
> +++ b/gdb/remote-notif.c
> @@ -0,0 +1,285 @@
> [...]
> +
> +extern struct remote_state *get_remote_state (void);
Don't declare external functions in .c files, it should live in a header.
next prev parent reply other threads:[~2012-08-24 19:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 2:26 [RCF 0/4] A general notification in GDB RSP Yao Qi
2012-08-24 2:26 ` [PATCH 3/4] de-couple %Stop from notification: gdbserver Yao Qi
2012-08-24 2:26 ` [PATCH 2/4] de-couple %Stop from notification: gdb Yao Qi
2012-08-24 16:52 ` Yao Qi
2012-08-24 19:00 ` dje [this message]
2012-08-30 6:40 ` Yao Qi
2012-08-24 2:26 ` [PATCH 4/4] new notification "TEST" Yao Qi
2012-08-24 2:26 ` [PATCH 1/4] new gdb_queue.h in common/ Yao Qi
2012-08-24 18:44 ` dje
2012-08-24 18:49 ` Doug Evans
2012-08-29 9:42 ` Yao Qi
2012-09-04 21:03 ` dje
2012-09-07 2:47 ` Yao Qi
2012-09-10 20:47 ` dje
2012-09-12 14:24 ` Yao Qi
2012-09-13 15:55 ` dje
2012-09-14 2:38 ` Yao Qi
2012-09-11 16:50 ` Tom Tromey
2012-08-24 17:53 ` [RCF 0/4] A general notification in GDB RSP Pedro Alves
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=20535.53033.569482.293453@ruffy2.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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