#354: Segfault in C code for RGB frames..
------------------------+---------------------------------------------------
Reporter: toots | Owner: admin
Type: Bugs | Status: new
Priority: 1 | Milestone: 1.0 beta
Component: Liquidsoap | Version: 0.9.2+svn
Keywords: | Mac: 1
Linux: 1 | Netbsd: 1
Other: 1 | Freebsd: 1
------------------------+---------------------------------------------------
Comment(by toots):
As far as I know, not using CAMLparam can save some CPU time but this
turns out to be negligible as soon as the C operations are more than
simple additions etc..
Additionally, another issue when releasing the OCaml thread is that the Gc
might change the location in memory of the caml objects. However, in our
case, we manipulate big arrays' memory pointers, which are allocated
outside of the Gc so these pointers should not be modified I believe.
Anyway, I have tried to run the code with CAMLparam and CAMLreturn, it
turns out to be even more instable. I am not sure about the origin of the
issue now but I think we will have a big segfault hunt to do for 1.0 beta
:)
(patch attached)
--
Ticket URL: <http://savonet.rastageeks.org/ticket/354#comment:6>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
------------------------------------------------------------------------------
_______________________________________________
Savonet-trac mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-trac
