seg. fault with Py_BuildValue?

[Christian Meesters]

Hi

I'm having trouble with Py_BuildValue. I was able to pinpoint the following
statement as the one causing a seg. fault with my script:

static PyObject * funcname(PyObject *self, PyObject *args) {
...
return Py_BuildValue("(OO)", x, y);
}
where x & y are both of type PyObject.

Any suggestions here? Do I need to handle the output of Py_BuildValue
somehow before returning? How? Need to decref x & y before returning?

TIA
Christian

[Diez B. Roggisch]

Christian Meesters wrote:

Just a guess - but according to the docs of Py_BuildValue it will return a
tuple already when given a format string of several format units.

What happens if you get rid of the ()?

Diez

[Christian Meesters]

> What happens if you get rid of the ()?

Can't see any difference.

[Christian Heimes]

Christian Meesters schrieb:

> Hi
>
> I'm having trouble with Py_BuildValue. I was able to pinpoint the following
> statement as the one causing a seg. fault with my script:
>
> static PyObject * funcname(PyObject *self, PyObject *args) {

> ....

> return Py_BuildValue("(OO)", x, y);
> }
> where x & y are both of type PyObject.
>
> Any suggestions here? Do I need to handle the output of Py_BuildValue
> somehow before returning? How? Need to decref x & y before returning?

Check if either x or y are NULL.

Christian

[Christian Meesters]

> Check if either x or y are NULL.

They aren't. Just did an explicit check.

[Christian Meesters]

Ok now, I know where the error is: "y" actually contained refcounts. This,
of course, is complete nonsense and causes the interpreter to crash at some
point.

Thanks to all of you: You helped at least to track down the problem.

Christian