From: Joel Brobecker <brobecker@adacore.com>
To: Liang Cheng <liang.cheng555@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] failed to attach to the same process after detaching in gdbserver multiprocess mode
Date: Mon, 27 Jun 2011 15:54:00 -0000 [thread overview]
Message-ID: <20110627155425.GE20676@adacore.com> (raw)
In-Reply-To: <BANLkTimd3V-uBLXOHmbvGP9hsg5x5XDZ3w@mail.gmail.com>
Liang,
Thanks for sending these patches in. I can't really approve your
patches since I don't have expertise in that area, but I can comment
on a couple of things:
- It's great that you take the time to explain what the problem is;
- Patches should have a ChangeLog entry to accompany them;
- One nit: It's awesome that you take the time to add comments
to document the code, and we don't use them often enough IMO.
But I think that, in general, we want the comments in the code
to say *why* you do what you do. And oh, comments should start
with a capital letter, and end with a period (and we always put
2 spaces after period, even before a closing */
> +
> + /* reset cont_thread */
> + cont_thread = null_ptid;
> return 0;
--
Joel
next prev parent reply other threads:[~2011-06-27 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 22:21 Liang Cheng
2011-06-27 15:54 ` Joel Brobecker [this message]
2011-06-27 17:10 ` Liang Cheng
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=20110627155425.GE20676@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=liang.cheng555@gmail.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