LDC 0.12.0 has been released

[David Nadlinger]

On Wed, Oct 23, 2013 at 6:53 PM, simendsjo <simendsjo at gmail.com> wrote:
> #0  0x00007ffff65149f3 in __epoll_wait_nocancel () from /usr/lib/libc.so.6
> #1  0x00007ffff79b7ae3 in ?? () from /usr/lib/libevent-2.0.so.5
> #2  0x00007ffff79a3660 in event_base_loop () from /usr/lib/libevent-2.0.so.5
> #3  0x00000000004cc4f4 in
> vibe.core.drivers.libevent2.Libevent2Driver.runEventLoop()
> (this=0x7ffff7ec98c0) at libevent2.d:122
> #4  0x00000000004d8357 in vibe.core.core.runEventLoop() () at core.d:84

This suggests that vibe.d is waiting for some event to trigger, but it
never does.

The easiest way to get an idea about what is going on would probably
be to sprinkle the code base with logging statements in the places
where events are added (i.e. printf-style debugging) and compare the
output with a DMD-compiled executable. Where exactly to add them
depends a bit on what you expect to happen in your application, but
you could of course also add them to pretty much every method in
vibe.core.drivers.libevent2.

David