Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: async patch (no. 4)
Date: Mon, 18 Jun 2007 05:00:00 -0000	[thread overview]
Message-ID: <18038.4452.524773.721616@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070618024611.GA12587@caradoc.them.org>

 > > I don't know how you can claim to uderstand almost none of it after you
 > > suggested to me to use SIGCHLD to interrupt the call to select instead of
 > > using threads.  I think some of these comments are based on looking at the
 > > previous (eponymous) patch (no. 4).
 > 
 > That's the only part of the patch I claim to understand at all.  It's
 > not that it's unintelligible - it's that I don't understand why any
 > given line is necessary.  Like, what does async_signal_hook do, and
 > why is it called from those particular places?  Why does async
 > behavior change where we need to claim the terminal?  Are the
 > quit_flag changes still necessary now that we've done some work on
 > QUIT?  Why don't the infrun changes break thread handling all over the
 > place?
 > 
 > All of these things are the same questions we'd ask for any patch.

Sure, but to be fair I think this is the first time you have asked them.

1) what does async_signal_hook do

   Firstly this patch only currently works for Linux.  That is because I don't
   know enough about other OSes and ISTR that you said others could extend
   easily it to them later.  For Linux, async_signal_hook is initialised to
   linux_nat_signal_hook in _initialize_linux_nat.  It is called (with
   different arguments) immediately before and after calls to select (or poll,
   if appropriate) and only if gdb is invoked with --async (event_loop_p != 0).

   On the first call, linux_nat_signal_hook sets up a handler,
   async_sigchld_handler, for SIGCHLD, that writes the return value of waitpid
   to the file descriptor that linux_nat_fetch_event reads from.
   linux_nat_fetch_event is called instead of my_waitpid with an asynchronous
   target in linux_nat_wait.  On the second call linux_nat_signal_hook
   restores the old signal mask.

I'll try to answer the other questions in due course, but I'd like to hear if
you think I'm making sense trying to answer this one first.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-06-18  5:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20  7:05 Nick Roberts
2007-01-12 18:31 ` Daniel Jacobowitz
2007-01-12 22:24   ` Nick Roberts
2007-01-12 23:03     ` Daniel Jacobowitz
2007-06-17  9:28       ` Nick Roberts
2007-06-17 15:21         ` Daniel Jacobowitz
2007-06-17 20:50           ` Nick Roberts
2007-06-18  2:46             ` Daniel Jacobowitz
2007-06-18  5:00               ` Nick Roberts [this message]
2007-06-18 11:32                 ` Daniel Jacobowitz
2007-06-18 21:48                   ` Nick Roberts

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=18038.4452.524773.721616@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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