Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add comments to linux-nat.c
Date: Sat, 14 Jun 2008 19:51:00 -0000	[thread overview]
Message-ID: <ulk17lt47.fsf@gnu.org> (raw)
In-Reply-To: <200806141829.05646.vladimir@codesourcery.com>

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 14 Jun 2008 18:29:05 +0400
> 
> 
> With the introduction of async mode, linux-nat.c became even more complex that it
> was, and it became apparent that some high-level comments are needed. So, I've grabbed
> Pedro and Dan on IRC and extracted the knowledge from their heads into a text file.
> Here's the result. OK?

Thanks.  I don't know anything about the subject matter, but I spotted
a few typos in the text:

> +threads. (2.4 has the __WALL flag).  So, it we use blocking waitpid, we might
                                            ^^
"if"

> +sigsuspend.  First, we use non-blocking waitpid to get if there's event

"to get if there's event" is not quite right, you probably wanted to
say "to find out if there's event".

> +in main debugged process and in cloned processes.  child processes.  As soon
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Something's wrong here.

> +The main design point is that every time GDB is outside linux-nat.c, we have a
> +SIGCLD handler installed that is called when something happens to the target
   ^^^^^^
SIGCLD or SIGCHLD?

> +Those waitpid calls, while blocking, are guarantied to always always have
                                                          ^^^^^^^^^^^^^
"always" twice.

> +of the pipe amoung the sources. When event loop starts to process the event
               ^^^^^^
"among"

> +us. Technically, it would be possible to add new events to the local queue but
> +it's about the same amount of work than blocking SIGCHLD.
                                      ^^^^^^^^^^^^^^^^^^^^^
"as blocking SIGCHLD"

> +enter/leave linux-nat.c is somewhat ugly. Unfortunately, GDB event loop is
> +home-grown is incapable to wait on any queue.

Something's wrong in "is home-grown is incapable".

> +tkill'd.  But we never let the SIGSTOP deliver; we always intercept and cancel
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"never let SIGSTOP be delivered".


  reply	other threads:[~2008-06-14 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14 18:19 Vladimir Prus
2008-06-14 19:51 ` Eli Zaretskii [this message]
2008-06-26 14:12 ` Daniel Jacobowitz
2008-06-26 15:56   ` Vladimir Prus
2008-06-26 16:03     ` Daniel Jacobowitz

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=ulk17lt47.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@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