December 2010 - libdispatch-dev - lists.macosforge.org

[PATCH] build libdispatch r196 under Linux
by Mark Heily 24 Dec '10

24 Dec '10

The following changes are needed to build libdispatch r196 under Linux. Please apply this patch to the trunk. Thanks, - Mark Index: configure.ac =================================================================== --- configure.ac (revision 196) +++ configure.ac (working copy) @@ -8,6 +8,7 @@ AC_CONFIG_AUX_DIR(config) AC_CONFIG_HEADER([config/config.h]) AC_CONFIG_MACRO_DIR([m4]) +AC_USE_SYSTEM_EXTENSIONS AM_MAINTAINER_MODE # Index: testing/shims/fgetln.c =================================================================== --- testing/shims/fgetln.c (revision 196) +++ testing/shims/fgetln.c (working copy) @@ -41,6 +41,7 @@ #include <stdio.h> #include <stdlib.h> +#include <string.h> #include <strings.h> #include <errno.h> Index: testing/shims/arc4random.c =================================================================== --- testing/shims/arc4random.c (revision 196) +++ testing/shims/arc4random.c (working copy) @@ -34,6 +34,7 @@ #include <sys/types.h> #include <sys/time.h> +#include <stdint.h> #include <stdlib.h> #include <fcntl.h> #include <unistd.h>

2 1

It's Christmas time and...
by Joakim Johansson 24 Dec '10

24 Dec '10

…a very nice present would be integration of the patches from Mark: —— Subject: [libdispatch-dev] [PATCH] various portability issues Date: 10 november 2010 02.51.03 CET -— :-) (then we can submit the required patches for passing the test suite next...) Wishing for a friendly SC! Cheers, Joakim

3 8

Canceling/releasing a suspended timer
by Kevin Wojniak 15 Dec '10

15 Dec '10

It appears that releasing a suspended timer is not allowed and will crash. Also, canceling the suspended timer does not appear to work and call the cancel handler. Are these correct assumptions? If so, then if I have a suspended timer, is the proper way to cancel or release it is to first resume? However I would imagine there is still the off chance that the timer could fire in between those calls to resume and cancel, requiring a flag to be set. Kevin

2 2

Some questions about source handling
by cee1 11 Dec '10

11 Dec '10

Hi all, Questions: 1. How does a source's event handler accesses data returned by kevent? Data returned by kevent will finally be recorded is ds_data field in _dispatch_source_latch_and_call. The event handler will be called with ds_handler_ctxt, which shoule be do_ctxt. "do_ctxt" can be set by function dispatch_set_context. The problem is: - If a handler need to access ds_data, we have to set a proper do_ctxt (e.g. a do_ctxt of source). That's not convenient. - "ds_data" is a member of dispatch_source_t, and dispatch_source_t is an opaque struct to client code. 2. We have custom source of type DISPATCH_SOURCE_TYPE_DATA_ADD and DISPATCH_SOURCE_TYPE_DATA_OR, and can use dispatch_source_merge_data to fire custom sources. Why we don't have an 'is_level' source? An "is_level" source may not make much sense, but can be attached with cancel handler, this may be useful in some cases. -- Regards, - cee1

3 4

libdispatch threads, blocked SIGINT and child process
by Thomas Clement 03 Dec '10

03 Dec '10

Hello, I have encountered a strange behavior when using libdispatch (OS X 10.6.5). I'm not sure if there is a bug in libdispatch or else what the correct fix is for me. I found myself in the situation of doing a fork/exec/waitpid from a libdispatch thread, the child process waiting for user input, then doing ctrl-c in my Terminal window. I would expect the child process to also be terminated, however the child process is still running, consuming lots of cpu (and its ppid is now 1 which is weird). I have noticed that libdispatch calls pthread_sigmask() when creating new threads blocking many signals. I have found that calling pthread_sigmask() in my dispatch_asynced code to unblock the SIGINT signal fixes the issue (the child process is also terminated when doing a ctrl-c in my Terminal window). You can reproduce the issue using the attached sample code (which uses launchctl as the child process but it could be anything else). You can run the process from the Terminal window (./sigdispatch_br) then doing ctrl-c and watching the child process from a "top". So, what do you guys think? Thanks, Thomas

2 2