This post was updated on .
Hi All ,
I am porting an already working code on Gst-1.0 to Gst-0.10. I have completed the changes and the code starts eworks on Gst-0.10 . The gst-0.10 code actually gets STRUCK at gst_set_state ( MUX , NULL ) ( Hence , return value is not there ) Roughly the pipeline is "videotestsrc -> clockoverlay -> timeoverlay -> queue -> avimux -> filesink " Could team member's please let me know what are the probable cause's that can cause gst-set_state to hang and not return from the call. I am falling short of debugging pointers to look for. Thanks , Ashish Kumar Mishra . |
On Di, 2016-03-15 at 22:29 -0700, Ashish Kumar Mishra wrote:
> Hi All , > > I am porting an already working code on Gst-1.0 to Gst-0.10. > I have completed the changes and the code starts eworks on Gst-0.10 . > > The gst-0.10 code actually gets STRUCK at *gst_set_state ( MUX , NULL > ) * ( > Hence , return value is not there ) > > Could team member's please let me know what are the probable cause's > that > can cause gst-set_state to hang and not return from the call. > > I am falling short of debugging pointers to look for. when it hangs? -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
Sorry for delay in reply ,
1) The pipeline is videotestsrc -> clockoverlay -> queue -> mux -> filesink 2) I am not getting any error or warning message on the console , it just gets struck at that point . If i press CTRL + C , the code terminates . I am not having any panic /segmentation fault /oops message on console. 3) To find the probable reason , i had started going through OMX default sample code. But I could not find any relevant pointers , hence i feel for this i should look at Gstreamer layer & not OMX. Could team members please let me know if my approach is correct w.r.t point (3) . Thanks , Ashish Kumar Mishra |
So can you run your 0.10 app in gdb, pause it when it hangs and take a look, "where" the threads are?
> On Apr 7, 2016, at 12:05, Ashish Kumar Mishra <[hidden email]> wrote: > > Sorry for delay in reply , > > 1) The pipeline is videotestsrc -> clockoverlay -> queue -> mux -> filesink > > 2) I am not getting any error or warning message on the console , it just > gets struck at that point . > If i press CTRL + C , the code terminates . I am not having any panic > /segmentation fault /oops message on console. > > 3) To find the probable reason , i had started going through OMX default > sample code. > But I could not find any relevant pointers , hence i feel for this i > should look at Gstreamer layer & not OMX. > > Could team members please let me know if my approach is correct w.r.t point > (3) . > > Thanks , > Ashish Kumar Mishra > > > > -- > View this message in context: http://gstreamer-devel.966125.n4.nabble.com/gst-set-state-MUX-NULL-get-s-HANGED-Porting-Gst-1-0-code-to-Gst-0-10-tp4676362p4676788.html > Sent from the GStreamer-devel mailing list archive at Nabble.com. > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
I would do that and report the observation
|
Attached is the bare minimum code for the same .
By changing the #define , the same code can be tested at GST-0.10 & GST-1.0 #define VERSION 1 ----> Gstreamer 1.6 ( Works ) #define VERSION 0 ----> Gstreamer 0.10 ( Mux hangs ) Please le me know if by simple code view , any logical mistake . I would share the GDB outcome shortly , as i need to check if GDB is working on our board. Thanks Ashish Kumar Mishra sample_code.c |
Free forum by Nabble | Edit this page |