search for: for_libxl

...efer the following logs for full information: **** [New Thread 0x7f8503695700 (LWP 20012)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007f84f671281e in libxl_osevent_occurred_timeout (ctx=<optimized out>, for_libxl=0x7f8503bbbc38) at libxl_event.c:1039 #2 0x00007f84f69439c7 in libxlDomainObjTimerCallback (timer=<optimized out>, timer_info=0x7f8503bb5930) at libxl/libxl_domain.c:216 #3 0x00007f8502ba6f7d in virEventPollDispatchTimeouts () at util/vireventpoll.c:451 #4 virEventPollRunOnce () at util/vi...

...86_64-linux-gnu/libpthread.so.0 #5 0x00007fc3349daa3d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fc337c4d7c0 (LWP 29169)): #0 0x0000000000000000 in ?? () #1 0x00007fc32ace881e in libxl_osevent_occurred_timeout (ctx=<optimized out>, for_libxl=0x7fc3380edf38) at libxl_event.c:1039 #2 0x00007fc32af199c7 in libxlDomainObjTimerCallback (timer=<optimized out>, timer_info=0x7fc3380e3310) at libxl/libxl_domain.c:216 #3 0x00007fc33717cf7d in virEventPollDispatchTimeouts () at util/vireventpoll.c:451 #4 virEventPollRunOnce () at util/vi...

...> **** > [New Thread 0x7f8503695700 (LWP 20012)] > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000000000000 in ?? () > (gdb) bt > #0 0x0000000000000000 in ?? () > #1 0x00007f84f671281e in libxl_osevent_occurred_timeout (ctx=<optimized > out>, for_libxl=0x7f8503bbbc38) at libxl_event.c:1039 > #2 0x00007f84f69439c7 in libxlDomainObjTimerCallback (timer=<optimized > out>, timer_info=0x7f8503bb5930) at libxl/libxl_domain.c:216 > #3 0x00007f8502ba6f7d in virEventPollDispatchTimeouts () at > util/vireventpoll.c:451 > #4 virEvent...

i installed both xen-4.2.1 and libvirt-1.2.0 from the source only. i moved with the latest version of libvrirt. i did the gdb in libvirt-1.2.0 and i raised the bug. Please find the following link for the bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1044838 regards, cooldharma06. On Wed, Dec 18, 2013 at 6:33 PM, Michal Privoznik <mprivozn@redhat.com>wrote: > On 18.12.2013

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on

...81ce940, event=0x7f793c30c2e0) at libxl/libxl_domain.c:534 #7 0x00007f793806f7c0 in egc_run_callbacks (egc=egc@entry=0x7ffdb79c7490) at libxl_event.c:1405 #8 0x00007f793806fb9d in libxl__egc_cleanup (egc=0x7ffdb79c7490) at libxl_event.c:1436 #9 libxl_osevent_occurred_fd (ctx=<optimized out>, for_libxl=0x7f78d80ec220, fd=27, events_ign=<optimized out>, revents_ign=<optimized out>) at libxl_event.c:1339 #10 0x00007f78fe3f9ac5 in libxlFDEventCallback (watch=11, fd=27, vir_events=1, fd_info=0x7f78d811c430) at libxl/libxl_driver.c:134 #11 0x00007f793b04a9c4 in virEventPollDispatchHandles...

...rt) calls libxl_osevent_occurred_timeout, in a multithreaded program those calls may be arbitrarily delayed in relation to other activities within the program. Specifically this means when ->timeout_deregister returns, libxl does not know whether it can safely dispose of the for_libxl value or whether it needs to retain it in case of an in-progress call to _occurred_timeout. The interface could be fixed by requiring the application to make a new call into libxl to say that the deregistration was complete. However that new call would have to be threa...