search for: event_callback

Allow Guestfs.t handle to be garbage collected, and add a regression test.

dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- kqueue.c: line 66 (event_callback): assertion failed: (io->refcount == 1) dovecot: Nov 24 12:49:06 Error: IMAP(user): Raw backtrace: 2 imap 0x0000000100068e82 default_fatal_finish + 41 -> 3 imap 0x0000000100068eed i_syslog_fatal_handler + 0 -> 4 imap 0x0000000100068687 i_info + 0 -> 5 imap...

...quot; close_connection EventMachine::stop_event_loop end end end EventMachine::run { EventMachine::open_datagram_socket "127.0.0.99", port, EchoServer } Gives the error d:/ruby/lib/ruby/gems/1.8/gems/eventmachine-0.8.1-x86-mswin32/lib/eventmachine.rb:959:in `event_callback'': EventMachine::ConnectionNotBound (EventMachine::ConnectionNotBound) from d:/ruby/lib/ruby/gems/1.8/gems/eventmachine-0.8.1-x86-mswin32/lib/eventmachine.rb:223:in `release_machine'' from d:/ruby/lib/ruby/gems/1.8/gems/eventmachine-0.8.1-x86-mswin32/lib/eventmachine...

--- generator/generator_gobject.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/generator/generator_gobject.ml b/generator/generator_gobject.ml index e4c175b..48ddbf0 100644 --- a/generator/generator_gobject.ml +++ b/generator/generator_gobject.ml @@ -391,7 +391,7 @@ let generate_gobject_optargs_source name optargs flags () = pr "G_DEFINE_TYPE(%s, guestfs_%s,

...d_doc then - pr "(**/**)\n"; - pr "\n"; ) external_functions_sorted; @@ -223,23 +230,30 @@ end class guestfs : ?environment:bool -> ?close_on_exit:bool -> unit -> object method close : unit -> unit + (** See {!Guestfs.close} *) method set_event_callback : event_callback -> event list -> event_handle + (** See {!Guestfs.set_event_callback} *) method delete_event_callback : event_handle -> unit + (** See {!Guestfs.delete_event_callback} *) method last_errno : unit -> int + (** See {!Guestfs.last_errno} *) method ocaml_handle...

...libruby18.so.18 #23 0x280a61c9 in rb_call0 () from /usr/local/lib/libruby18.so.18 #24 0x280a66c6 in rb_call () from /usr/local/lib/libruby18.so.18 #25 0x280a69f9 in vafuncall () from /usr/local/lib/libruby18.so.18 #26 0x280a6a3c in rb_funcall () from /usr/local/lib/libruby18.so.18 #27 0x282a22f7 in event_callback () from /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/rubyeventmachine.so #28 0x2829f402 in EventMachine_t::_RunTimers () from /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/rubyeventmachine.so #29 0x2829ed4c in EventMachine_t::Run () from /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/rubyeven...

...fcount = 0, fd = 0} (gdb) print *io->next $18 = {io = {condition = 0, callback = 0, context = 0x471a982100000000}, prev = 0x0, next = 0x2f766f6c2f686f6d, refcount = 1697606764, fd = 1870226479} (gdb) print *current_ioloop->io_files $35 = {io = {condition = IO_READ, callback = 0x1e9284 <event_callback>, context = 0x342080}, prev = 0x0, next = 0x320140, refcount = 1, fd = 11} (gdb) print *current_ioloop->io_files->next $36 = {io = {condition = IO_ERROR, callback = 0x12ca70 <log_error_callback>, context = 0x0}, prev = 0x320a00, next = 0x3200c0, refcount = 1, fd = 2} (gdb) pr...

Using 'ocamlfind ocamldoc' is much faster than running 'ocamldoc' directly, because ocamlfind will run the native code program 'ocamldoc.opt' if it is available. This change approximately halves the time taken to compile the ocaml bindings. --- ocaml/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ocaml/Makefile.am b/ocaml/Makefile.am index

Was running dovecot-1.0.rc2 but many stale imap processes (only one user of IMAP). Switched to dovecot-1.0.rc6 but problem continued. This is on FreeBSD 4 something. Maybe it has bug with kqueue?? I read messages about the stale imap processes on the list. It seems to hit *BSD systems. But email about new release candidate indicated it should be fixed. I read on the pkgsrc commit list

...o ways. First, by starting a new thread inside the EM::run{..}. Even with limited understanding of threads in ruby this didn''t make sense, but I tried it anyway - no joy. The first part of the EM error is below: /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.0/lib/eventmachine.rb:793:in `event_callback'': EventMachine::ConnectionNotBound (EventMachine::ConnectionNotBound) from /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.0/lib/eventmachine.rb:201:in `run_machine'' from /usr/lib/ruby/gems/1.8/gems/eventmachine-0.7.0/lib/eventmachine.rb:201:in `run'' Second,...

I rewrote much of the kqueue code since the old code didn't handle properly the case when both input and output I/O handlers were added to the same file descriptor with different callbacks. This is done commonly in Dovecot, so I'm wondering why more people didn't complain about problems with it.. :) I don't anyway have access to any BSDs so the code is completely untested. Please

As promised, here it is finally. v1.0 is getting nearer and I want people to start looking at Dovecot's sources. Getting some more help with development would be nice, but I'd also like to hear if there are any hidden bugs in the code. So, one week from now I'll start offering 1000 EUR for the first person to point out a remotely exploitable security hole in Dovecot. See

...ed. If you didn't call the "close" function explicitly, the handle would not be closed until the whole program exited. This has now been fixed so handles will be garbage collected in the usual way. This changes the API of the OCaml function "Guestfs.event_callback". Note that non-C language bindings are not covered by the libguestfs API/ABI guarantee, although we try hard not to change them, but in this case it was essential in order to fix this very serious bug. Inspection Alpine Linux and the APK package manager,...

...); + DEFINE(OFFSET_VCPU_TTBR0, offsetof(struct vcpu_guest_context, ttbr0)); + DEFINE(OFFSET_VCPU_TTBR1, offsetof(struct vcpu_guest_context, ttbr1)); + DEFINE(OFFSET_VCPU_TTBCR, offsetof(struct vcpu_guest_context, ttbcr)); + //DEFINE(OFFSET_HYPERVISOR_CALLBACK, offsetof(struct vcpu_guest_context, event_callback)); + //DEFINE(OFFSET_FAILSAFE_CALLBACK, offsetof(struct vcpu_guest_context, failsafe_callback)); BLANK(); return 0; diff -r 28a6038da99f xen/arch/arm/xen/entry.S --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/xen/arch/arm/xen/entry.S Fri Feb 03 17:47:16 2012 +0900 @@ -0,0 +1,596 @@ +/* +...

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be