public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: frysk <frysk@sourceware.org>
Subject: Re: Notes meeting 2007-03-28
Date: Thu, 29 Mar 2007 17:26:00 -0000	[thread overview]
Message-ID: <1175189198.4508.9.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <460A81EA.1010507@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 453 bytes --]

On Wed, 2007-03-28 at 10:55 -0400, Elena Zannoni wrote:
> plain text document attachment (frysk-20070328)

Thanks for making notes Elena.

> Mark suggests using waitid(). 

If that works, then we would get some extra info through the siginfo_t
that we now have to query through additional ptrace calls). I see now
that waitpid does not support the _WALL option and it seems we need that
or we won't get to wait on all tasks in a process :{


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-03-29 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-28 15:03 Elena Zannoni
2007-03-29 17:26 ` Mark Wielaard [this message]

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=1175189198.4508.9.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=frysk@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).