Description:
------------
In the test example below, if you happen to throw an uncaught Exception, the application get's stuck in an infinite loop. This is probably not the way it should work, and the dispatch method should exit with EINTR. 

Per the libevent library, it says dispatch can exit. "It [A callback] can return -1 to indicate an error to the event library, causing event_dispatch() to terminate with errno set to EINTR."


Reproduce code:
---------------
<?php

dl('event.so');


event_init();

// called when user hits ^C. Should stop the dispatcher b/c no more scheduled events.
function stop($sig) {
    global $s;
    global $p;
    echo "You got signal $sig.\n";
    throw new Exception("Test Exception");
}

function periodic()
{
    print time() ."\r";
    return true;
}

$s = event_handle_signal(2, 'stop');
event_schedule($s);

$p = event_timeout('periodic', null,  0, 5000, EV_PERSIST );
event_schedule($p);

echo "Going into dispatch loop: at t= " . time() . "\n";
event_dispatch();

echo "all done\n";

?>


Expected result:
----------------
The dispatch loop should terminate and the message "all done" printed out to the screen.

Actual result:
--------------
Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

Warning: event_dispatch(): callback failed in /tmp/t.php on line 34

....forever