Message-ID: <003201c3d5f5$5a3bfb10$0300a8c0 at behemoth> From: =?iso-8859-1?Q?Andrei_de_Ara=FAjo_Formiga?= To: Subject: Bug in Gdk.Input.add Date: Thu, 8 Jan 2004 11:40:24 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I think this is probably a bug or a limitation with GTK+/GDK in windows and not with lablgtk, but I'm exposing it here so people with more knowledge can check it. Using OCaml 3.07 native version on windows, LablGTK 1.2.6 (from lablgtk-1.2.6-ocamlwin-3.07.zip) and the GTK 1.3 DLLs (from gtk-1.3.0-dlls-win32.zip). A transcript of a session that reproduces the error follows: D:\Test\caml\>lablgtk Objective Caml version 3.07 # #load "unix.cma";; # let sc = Unix.socket Unix.PF_INET Unix.SOCK_STREAM 0;; val sc : Unix.file_descr = # let id = Gdk.Input.add sc ~cond:`READ ~callback:(fun () -> ());; (ocaml:2244): GLib-WARNING **: giowin32.c:1624: 7025392 is neither a file descriptor or a socket (ocaml:2244): GLib-CRITICAL **: file giochannel.c: line 471 (g_io_add_watch_full): assertion `channel != NULL' failed (ocaml:2244): GLib-CRITICAL **: file giochannel.c: line 104 (g_io_channel_unref): assertion `channel != NULL' failed val id : Gdk.Input.callback_id = # I checked it with a "real" callback and it's never called. The same code on linux runs fine. --- []s, Andrei de A. Formiga