search for: forcably

...tead: %eh_select8.i = tail call i32 (i8*, i8*, ...)* @llvm.eh.selector.i32( i8* %eh_ptr.i, i8* bitcast (i32 (...)* @__gxx_personality_v0 to i8*), i8* null) then the unwinder does branch to lpad.i. Then the _Unwind_Resume call causes a branch to lpad2 and all works perfectly. This is why I forcably push a catch-all at the end of each selector call: because then if an exception unwinds through an invoke, control always branches to the landing pad, which is what LLVM invoke semantics require and the inliner has exploited. Unfortunately it seems this breaks the Darwin unwinder. It is true that...

...ay and playing with the initial config's, etc. It's working, but have a ways to go before it could be considered usable. The box was not designed to "register" like sip phones do. The incoming pstn line is an ordinary 2-wire analog US pots line, and I'm using canreinvite=no to forcably keep * in the middle for now. Questions: 1. The 1204 answers incoming pstn calls correctly, cycles through the invite/ trying/ringing (I have * config'ed to simply ring an internal sip phone for testing purposes), and I answer the call just fine from the sip phone. When I hang up the sip phon...

(Mail system seems to have eaten this, sorry if it's a repeat) On Dec 8, 2007, at 12:48 AM, Duncan Sands wrote: > Hi Dale, > >> - Why was C++ claiming that every selector has a catch-all handler? > > this is easy: because the semantics of invoke require it. Yes, > really. > If unwinding reaches an invoke then control is required to jump to the > unwind basic

...i32 (i8*, i8*, ...)* > @llvm.eh.selector.i32( i8* %eh_ptr.i, i8* bitcast (i32 (...)* > @__gxx_personality_v0 to i8*), i8* null) > then the unwinder does branch to lpad.i. Then the _Unwind_Resume > call causes a branch to > lpad2 and all works perfectly. > > This is why I forcably push a catch-all at the end of each selector > call: because then if an > exception unwinds through an invoke, control always branches to the > landing pad, which is what > LLVM invoke semantics require and the inliner has exploited. > > Unfortunately it seems this breaks the...

...= int64 + + val to_string: t -> string + end + + module Watchdog : sig + type t = [ + | `None (** No action, watchdog ignored *) + | `Pause (** Guest CPUs are paused *) + | `Reset (** Guest CPUs are reset *) + | `Poweroff (** Guest is forcably powered off *) + | `Shutdown (** Guest is requested to gracefully shutdown *) + | `Debug (** No action, a debug message logged *) + | `Unknown of int (** newer libvirt *) + ] + + val to_string: t -> string + end + + module Io_error : sig + (** Represents...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all