Date: Fri, 11 Dec 1998 09:51:16 +0100 From: sthaug@nethelp.no To: archie@whistle.com Cc: jkh@zippy.cdrom.com, eivind@yes.no, vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. Message-ID: <2490.913366276@verdi.nethelp.no> In-Reply-To: Your message of "Thu, 10 Dec 1998 22:06:52 -0800 (PST)" References: <199812110606.WAA22141@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Well, this brings up an unrelated question. I've written a little
> library that comes in very handy in situations like this (I have
> heard there are similar things out there but this was a custom job).
>
> Basically, it allows you to write an event driven program, where
> each event is handled atomically from all others, without resorting
> to threads and libc_r. An event is a file descriptor read/write
> condition, a timer timeout, or a signal receipt.
This would be good to have in the system. Have you compared your lib
with Paul Vixie's eventlib, part of BIND 8.1.x? The man page is in
src/lib/isc/eventlib.mdoc in the 8.1.2 source. A small part is
included below.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
----------------------------------------------------------------------
NAME
evConnFunc, evFileFunc, evStreamFunc, evTimerFunc, evWaitFunc, evCreate,
evDestroy, evGetNext, evDispatch, evDrop, evMainLoop, evConsTime,
evTimeSpec, evTimeVal, evAddTime, evSubTime, evCmpTime, evNowTime,
evLastEventTime, evSetTimer, evResetTimer, evClearTimer, evSetIdleTimer,
evTouchIdleTimer, evClearIdleTimer, evWaitFor, evDo, evUnwait, evDefer,
evSelectFD, evDeselectFD, evWrite, evRead, evCancelRW, evTimeRW,
evUntimeRW, evListen, evConnect, evCancelConn, evHold, evUnhold,
evTryAccept, evConsIovec, evSetDebug, evPrintf - event handling library
...
DESCRIPTION
This library provides multiple outstanding asynchronous timers and I/O to
a cooperating application. The model is similar to that of the X Toolk
it, in that events are registered with the library and the application
spends most of its time in the evMainLoop() function. If an application
already has a main loop, it can safely register events with this library
as long as it periodically calls the evGetNext() and evDispatch() func
tions. (Note that evGetNext() has both polling and blocking modes.)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2490.913366276>