Bug 733297 - ruby event handlers fail with "exception in callback: wrong argument type Proc (expected Data)"
Summary: ruby event handlers fail with "exception in callback: wrong argument type Pro...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libguestfs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-25 11:53 UTC by Richard W.M. Jones
Modified: 2011-08-26 10:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-26 10:09:44 UTC


Attachments (Terms of Use)
test.rb (479 bytes, application/x-ruby)
2011-08-25 11:53 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2011-08-25 11:53:59 UTC
Created attachment 519823 [details]
test.rb

Description of problem:

See attached program.  Note the bug was found by Marek Goldmann
in Boxgrinder.

Version-Release number of selected component (if applicable):

libguestfs 1.10 through 1.13.7.

How reproducible:

100%

Steps to Reproduce:
1. Run the attached program.
2.
3.
  
Actual results:

At the end of the program the even handler gets into a funny
state where it gives lots of errors like this:

libguestfs: exception in callback: wrong argument type Proc (expected Data)libguestfs: exception in callback: wrong argument type Proc (expected Data)libguestfs: exception in callback: wrong argument type Proc (expected Data)libguestfs: exception in callback: wrong argument type Proc (expected Data)libguestfs: exception in callback: wrong argument type Proc (expected Data)...

Expected results:

Should not do that.

Additional info:

Comment 1 Richard W.M. Jones 2011-08-25 13:06:43 UTC
I won't pretend I really understand what's going on here,
but I have posted this workaround:

https://www.redhat.com/archives/libguestfs/2011-August/msg00148.html

BTW the error messages look scary but are completely
benign -- just some unwanted output to stderr.  It doesn't
crash the Ruby interpreter or libguestfs.


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