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

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

[PATCH] various portability issues
by Mark Heily 10 Nov '10

10 Nov '10

I have attached a collection of patches that allows libdispatch to build on Linux and Solaris. Many thanks to Joakim Johansson for providing the Solaris patches and testing everything. The commands I used to build on Linux are: CC="clang" LD="llvm-ld-2.8" CFLAGS="-I/usr/local" \ LDFLAGS="-L/usr/local" LIBS="-lbsd" ./configure && make The commands Joakim used to build on Solaris are: ./configure CFLAGS="-m64 -I/usr/local/include" \ LDFLAGS="-L/usr/local/lib” gmake Please review these and consider them for inclusion in the trunk. Regards, - Mark

1 0

BUG in libdispatch: 10F569 - 1730 - 0x11
by Ruben Laguna 04 Nov '10

04 Nov '10

Hi, My system (MacBook Pro) is crashing/freezing regularly 20 seconds after a wake up and the last message in the Console.app before the crash is a SystemUIServer[184] BUG in libdispatch: 10F569 - 1730 - 0x11 I downloaded the git repo to find out what this means and if it is really related to my system freeze. according to queue.c the format of this log is _dispatch_log("BUG in libdispatch: %s - %lu - 0x%lx", _dispatch_build, (unsigned long)line, val); So build 10F569, line 1730 (which file?), value 0x11. Anyone can tell me exactly what this error log means , how to workaround it or point me to the right forum to ask? Thanks /Rubén -- /Rubén

4 4

Patch submissions for Solaris compatibility
by Joakim Johansson 04 Nov '10

04 Nov '10

I submitted a few patches back in July for Solaris portability (enough to get libdispatch through most of the test suite when built with gcc together with libkqueue/libpthread_workqueue) - was there any (stylistic or other) issues with those that I should address for them being considered, or ...? Cheers, Joakim

1 0