By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,629 Members | 1,222 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,629 IT Pros & Developers. It's quick & easy.

SWIG callback problem on win32

P: n/a
Hi,

I tried to build the swig: callback example,
but when I run the runme.py file I get a message box:
abnormal program termination

The error appears in already in the first line of the python
callback generation:

# Add a Python callback (caller owns the callback, so we
# disown it first by calling __disown__).

caller.setCallback(PyCallback().__disown__())
caller.call()
caller.delCallback()

When I call only PyCallback().__disown__()
alone, the error appears, too.

Anybody knows a solution?

Thanks a lot,

Markus
Jul 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Markus von Ehr schrieb:
Hi,

I tried to build the swig: callback example,
but when I run the runme.py file I get a message box:
abnormal program termination

The error appears in already in the first line of the python
callback generation:

# Add a Python callback (caller owns the callback, so we
# disown it first by calling __disown__).

caller.setCallback(PyCallback().__disown__())
caller.call()
caller.delCallback()

When I call only PyCallback().__disown__()
alone, the error appears, too.

Anybody knows a solution?

Thanks a lot,

Markus

I made a new trial:

The error appears in the following line of the
Callback class:
_camera_callback.disown_Callback(self)

I guess the problem is in the
static PyObject *_wrap_disown_Callback
function?
How could I get rid of it?

Thanks for any hints to get rid of this error.

Markus

PS
The application is a C++ Thread providing a callback function,
when a new camera image on the firewire bus is available.
Then I want to inform a python object that it can fetch the new
image data.

Jul 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.