search for: l250

...id=1kB3uN-0006ar-HU Adding the line "pipelining_connect_advertise_hosts =" to Exim's config fixes the issue by disabling X_PIPE_CONNECT. Is this a bug in Exim or is Dovecot being too strict? Thanks, Alec [1] https://github.com/dovecot/core/blob/2.3.11.3/src/lib-smtp/smtp-syntax.c#L250

...t before returning an error to set the errno that nbdkit will use. In OCaml plugins we have to go through some hoops to convert OCaml errno (which use a different numbering) to system errno: https://github.com/libguestfs/nbdkit/blob/904c4e5fdca557d6d25a60e6fb12fa058263481e/plugins/ocaml/NBDKit.ml#L250 The other issue (from golang bindings) was threads. Does Rust use native system pthreads? If it does then there shouldn't be an issue. golang implements its own green threads and that was a problem. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Rea...

...o > set the errno that nbdkit will use. In OCaml plugins we have to go > through some hoops to convert OCaml errno (which use a different > numbering) to system errno: > > > https://github.com/libguestfs/nbdkit/blob/904c4e5fdca557d6d25a60e6fb12fa058263481e/plugins/ocaml/NBDKit.ml#L250 > > The other issue (from golang bindings) was threads. Does Rust use > native system pthreads? If it does then there shouldn't be an issue. > golang implements its own green threads and that was a problem. > > Rich. > > -- > Richard Jones, Virtualization Group, Red...

..."pipelining_connect_advertise_hosts =" to Exim's config > fixes the issue by disabling X_PIPE_CONNECT. > > Is this a bug in Exim or is Dovecot being too strict? > > Thanks, > Alec > > [1] https://github.com/dovecot/core/blob/2.3.11.3/src/lib-smtp/smtp-syntax.c#L250 Dovecot follows the standards as strict as reasonable, with some workarounds for the bad code out there. Exim is in violation of RFC 5321, Section 4.1.1.1: ehlo-ok-rsp = ( "250" SP Domain [ SP ehlo-greet ] CRLF ) / ( "250-" Domain [ SP ehlo-greet...

...> At that point we ran out of time we could spend on this. So we postponed the > feature, hoping for Microsoft to come up with a solution at some point. > Giving it another try today, I think this looks promising: > https://github.com/dotnet/llilc/blob/master/lib/Jit/EEMemoryManager.cpp#L250 > > Processing .pdata section entries, it creates and allocates unwind blocks > and funclets (handlers for catch & finally) for CLR managed exceptions. It's > probably not directly applicable to native exception handling, but it may > provide useful information. Also there is...

...this. So we postponed >> > the >> > feature, hoping for Microsoft to come up with a solution at some point. >> > Giving it another try today, I think this looks promising: >> > >> > https://github.com/dotnet/llilc/blob/master/lib/Jit/EEMemoryManager.cpp#L250 >> > >> > Processing .pdata section entries, it creates and allocates unwind >> > blocks >> > and funclets (handlers for catch & finally) for CLR managed exceptions. >> > It's >> > probably not directly applicable to native exception han...

Hi Bjoern, I'm trying to make exceptions run. I have an Object file with a function, > throwing a 1 and a second function which should catch the 1. Normal JITTING > under Windows showed me, that I have an unresolved reference to the virtual > table of type_info. Some experiments later I was able to load "msvcrt.lib" > as an archive and could resolve the reference. Nice -

> I tried loading the "msvcrt.lib" as a archive. That was... a bad idea! > I get a Exception while loading: > Assertion failed: ((int64_t)Result <= INT32_MAX) && "Relocation > overflow", file > \lib\executionengine\runtimedyld\Targets/RuntimeDyldCOFFX86_64.h, line 81 It's a limitation of the COFF/PE format and unrelated to exceptions. This patch