caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eric Cooper <ecc@cmu.edu>
To: caml-list@yquem.inria.fr, caml-list@inria.fr
Subject: Re: [Caml-list] LablGTK app maxes out CPU
Date: Tue, 4 Jul 2006 16:21:17 -0400	[thread overview]
Message-ID: <20060704202117.GB15987@localhost> (raw)
In-Reply-To: <44AAC8EE.1060805@gushee.net>

On Tue, Jul 04, 2006 at 02:00:46PM -0600, Matt Gushee wrote:
> Eric Cooper wrote:
> >Try making the fd nonblocking before you create the glib channel:
> >    Unix.set_nonblock msg_fd;
> 
> That's how it was originally. But if you look again at my code, you can 
> see that the version with Unix.O_NONBLOCK is commented out. That's 
> because on one of my machines (the one with a newer version of GTK and 
> LablGTK, I believe), I got exceptions every time the program tried to 
> read the input.

Right, me too.  I use code like this to read from the channel inside
the watcher:

let try_read chan ~buf ~pos ~len =
  try Some (Glib.Io.read chan ~buf ~pos ~len)
  with Glib.GError "g_io_channel_read: G_IO_ERROR_AGAIN" -> None

-- 
Eric Cooper             e c c @ c m u . e d u


  reply	other threads:[~2006-07-04 20:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 18:30 Matt Gushee
2006-07-04 18:59 ` [Caml-list] " Matt Gushee
2006-07-04 19:12 ` Eric Cooper
2006-07-04 20:00   ` Matt Gushee
2006-07-04 20:21     ` Eric Cooper [this message]
2006-07-05 23:24       ` Matt Gushee
     [not found]         ` <Pine.LNX.4.64.0607060354120.6166@home.oyster.ru>
2006-07-06  0:27           ` Matt Gushee
2006-07-06  2:46         ` Matt Gushee
2006-07-06 16:51         ` Jerome Vouillon
2006-07-06 19:16           ` Matt Gushee
2006-07-06 23:51           ` Matt Gushee
2006-07-07  1:26             ` SOLVED -- " Matt Gushee
2006-07-07 13:40             ` Jerome Vouillon

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=20060704202117.GB15987@localhost \
    --to=ecc@cmu.edu \
    --cc=caml-list@inria.fr \
    --cc=caml-list@yquem.inria.fr \
    /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 NNTP newsgroup(s).