Uhmm, my apologies I've just found out the cause for this issue, it's not libuv's fault as it seems that the library I am working with is causing some kind of code corruption.
Thank you anyway for your help :). Am Sonntag, 27. März 2016 08:46:07 UTC+2 schrieb [email protected]: > > I am currently working on an addon for node and it requires libuv's async > feature but somehow I am getting a segfault when creating an async handle > and immediately destroying it. > > Why is this happening and what am I doing wrong? > > > static uv_async_t asyncHandle; > > static void Callback(uv_async_t* handle) { > } > > void Function(const Nan::FunctionCallbackInfo<v8::Value>& info) { > uv_async_init(uv_default_loop(), &asyncHandle, Callback); > } > > void Function2(const Nan::FunctionCallbackInfo<v8::Value>& info) { > uv_close(reinterpret_cast<uv_handle_t*>(&asyncHandle), nullptr); > } > > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
