Passed-through **kwargs segfaults
12 views
Skip to first unread message
Mike Boers
Nov 20, 2015, 2:57:15 PM11/20/15
to cython-users
Hey all!
I just had a segfault issue with PyAV, in which av.container.input.InputContainer.demux passes all kwargs straight through to av.container.streams.Streams.get.
This commit was my workaround.
I've attached (what I believe to be) the relevant sections of the generated C before and after that "fix". It seems that __pyx_v_kwargs manages to be set to NULL, and then INCREFed. I'm not familiar with Cython's internals, but this seems plausible to me.
I'm sure I'm likely doing something I shouldn't in various __cinit__ and __dealloc__, etc., but this feels like it could be a bug in Cython. I tried several way to reduce it (if it were a bug), but wasn't able to manage it.
Any thoughts?
Thanks,
Mike
I just had a segfault issue with PyAV, in which av.container.input.InputContainer.demux passes all kwargs straight through to av.container.streams.Streams.get.
This commit was my workaround.
I've attached (what I believe to be) the relevant sections of the generated C before and after that "fix". It seems that __pyx_v_kwargs manages to be set to NULL, and then INCREFed. I'm not familiar with Cython's internals, but this seems plausible to me.
I'm sure I'm likely doing something I shouldn't in various __cinit__ and __dealloc__, etc., but this feels like it could be a bug in Cython. I tried several way to reduce it (if it were a bug), but wasn't able to manage it.
Any thoughts?
Thanks,
Mike
Reply all
Reply to author
Forward
0 new messages