I'm just creating a placeholder for this bug. Description of problem: While executing wait_ready in ruby bindings I get this stacktrace: http://gist.github.com/144389 Version-Release number of selected component (if applicable): [oddthesis@bolek-f11 ~]$ rpm -qa | grep libguestfs libguestfs-1.0.54-2.fc11.x86_64 ocaml-libguestfs-1.0.54-2.fc11.x86_64 libguestfs-javadoc-1.0.54-2.fc11.x86_64 libguestfs-java-1.0.54-2.fc11.x86_64 python-libguestfs-1.0.54-2.fc11.x86_64 ruby-libguestfs-1.0.54-2.fc11.x86_64 libguestfs-java-devel-1.0.54-2.fc11.x86_64 libguestfs-devel-1.0.54-2.fc11.x86_64 libguestfs-debuginfo-1.0.51-1.fc11.x86_64 perl-libguestfs-1.0.54-2.fc11.x86_64 ocaml-libguestfs-devel-1.0.54-2.fc11.x86_64 How reproducible: Not always. Now searching for an environment to reproduce, I'll update this bug if I'll have more information. Steps to Reproduce: 1. 2. 3. Actual results: Error. Expected results: No error. Additional info:
(In reply to comment #0) > How reproducible: > > Not always. Now searching for an environment to reproduce, I'll update this bug > if I'll have more information. Stack trace isn't really much use to us, but a short ruby program which reproduces the bug would be. If your program is repeatedly opening and closing guestfs handles (from the same program), then there is a known bug which causes segfaults, with a patch to fix it which I'll attach here.
Created attachment 351237 [details] libguestfs-properly-close-and-unregister.patch This is a patch, not yet applied upstream, which fixes a bug where repeatedly opening and closing libguestfs handles in a single program would sometimes cause a segfault.
After quick testing I can say, that release 1.0.57 resolved my issue.
Reported as fixed.