[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-smalltalk] Crash on sockets and Exceptions
|
From: |
Holger Hans Peter Freyther |
|
Subject: |
Re: [Help-smalltalk] Crash on sockets and Exceptions |
|
Date: |
Mon, 13 Jun 2011 19:44:11 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10 |
On 06/13/2011 07:28 PM, Holger Hans Peter Freyther wrote:
> so is IS_OOP(NULL) well defined, giving other code.. I think it is not safe.
> So do we add a null check there? or do we use another OOP for aysnc file
> notifications?
diff --git a/libgst/sysdep/posix/events.c b/libgst/sysdep/posix/events.c
index ab2a88e..b40d7aa 100644
--- a/libgst/sysdep/posix/events.c
+++ b/libgst/sysdep/posix/events.c
@@ -342,6 +342,7 @@ file_polling_handler (int sig)
if (num_used_pollfds > 0)
{
static async_queue_entry e = { async_signal_polled_files, NULL, NULL };
+ e.data = _gst_true_oop;
_gst_async_call_internal (&e);
}
any feelings on making the NULL, FALSE, TRUE OOP const?