Cause:
libguestfs was not setting an error during some appliance launch failures. Python bindings assume that the error string is not NULL, and would segfault if it was NULL.
Consequence:
Python programs could segfault when 'g.launch()' was called under some circumstances.
Fix:
libguestfs now sets the error string on all failure paths in launch, and the Python bindings have been fixed not to segfault.
Result:
Python programs won't segfault when calling 'g.launch()'

Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause:
libguestfs was not setting an error during some appliance launch failures. Python bindings assume that the error string is not NULL, and would segfault if it was NULL.
Consequence:
Python programs could segfault when 'g.launch()' was called under some circumstances.
Fix:
libguestfs now sets the error string on all failure paths in launch, and the Python bindings have been fixed not to segfault.
Result:
Python programs won't segfault when calling 'g.launch()'

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2012-0774.html

Note

You need to
log in
before you can comment on or make changes to this bug.