From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches\@sourceware.org ml"
<gdb-patches@sourceware.org>
Subject: Re: RFA: remote.c : allow long monitor cmds + allow user to C-c
Date: Tue, 24 Jan 2012 04:43:00 -0000 [thread overview]
Message-ID: <m38vkxhib1.fsf@redhat.com> (raw)
In-Reply-To: <1327350423.2215.6.camel@soleil> (Philippe Waroquiers's message of "Mon, 23 Jan 2012 21:27:03 +0100")
Hello Philippe,
Thanks for the patch. Do you have copyright assignment?
Some formatting nits.
On Monday, January 23 2012, Philippe Waroquiers wrote:
> On Mon, 2012-01-23 at 12:31 +0000, Pedro Alves wrote:
>> Please use "cvs diff -up", or put "diff -up" in your ~/.cvsrc file.
> Oops, 2nd trial.
>
> Index: gdb/ChangeLog
> ===================================================================
> RCS file: /cvs/src/src/gdb/ChangeLog,v
> retrieving revision 1.13761
> diff -u -p -r1.13761 ChangeLog
> --- gdb/ChangeLog 20 Jan 2012 10:31:25 -0000 1.13761
> +++ gdb/ChangeLog 23 Jan 2012 20:22:22 -0000
> @@ -1,3 +1,8 @@
> +2012-01-22 Philippe Waroquiers <philippe.waroquiers@skynet.be>
> +
> + * remote.c (remote_rcmd): use getpkt_sane to detect timeout
> + and continue the loop. Add QUIT statement.
First letter shall be uppercase. Two spaces after period, before
beginning a new sentence. The date must also be updated if/when you
commit.
> Index: gdb/remote.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/remote.c,v
> retrieving revision 1.478
> diff -u -p -r1.478 remote.c
> --- gdb/remote.c 20 Jan 2012 09:47:32 -0000 1.478
> +++ gdb/remote.c 23 Jan 2012 20:22:24 -0000
> rs->buf[0] = '\0';
> - getpkt (&rs->buf, &rs->buf_size, 0);
> + if (getpkt_sane (&rs->buf, &rs->buf_size, 0) == -1)
> + {
> + /* Timeout. Continue to (try to) read responses.
> + This is better than stopping with an error, assuming the stub
> + is still executing the (long) monitor command.
> + If needed, the user can interrupt gdb using C-c, obtaining
> + an effect similar to stop on timeout. */
> + continue;
> + }
Same formatting issues here in this comment: two spaces after period.
I know almost nothing about this part of the code, but as far as I have
seen, the patch looks OK. I am not a maintainer, however.
--
Sergio
next prev parent reply other threads:[~2012-01-24 3:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 9:42 Philippe Waroquiers
2012-01-23 12:43 ` Pedro Alves
2012-01-23 21:09 ` Philippe Waroquiers
2012-01-24 4:43 ` Sergio Durigan Junior [this message]
2012-01-24 4:52 ` Philippe Waroquiers
2012-02-02 22:13 ` (ping) " Philippe Waroquiers
2012-02-03 20:28 ` Stan Shebs
2012-02-03 22:39 ` Philippe Waroquiers
2012-02-06 19:38 ` 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=m38vkxhib1.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=philippe.waroquiers@skynet.be \
/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