Aw: Re: Re: Re: GStreamer application access violation in random locations

[pfarmer]

There may be some valgrind alternatives on Windows, but I do not have used
any so far. From a short survey the free versions lacks on an 'attach to
running process' capability. And hence not usable for debugging in a running
Simulink instance. 

It is meanwhile quite evident that the  gst_debug_log_valist error is not
related at all the original problem:
GStreamer application access violation in random locations while running in
Simulink.

> It looks like a case of general memory corruption at an earlier point that
> is showing its
> effects now. 

How does that work? 
Could that be prevented at all, if the SIGSEGVs are generated by Simulink?
(except of being it fixed by Mathworks the Simulink programmers). 



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/GStreamer-application-access-violation-in-random-locations-tp4674999p4675404.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.