GNOME Bugzilla – Bug 339872
filesrc can't work in pull mode (XScale)
Last modified: 2006-05-09 10:05:50 UTC
Please describe the problem: the same source code works well at x86 both win32 and linux. but when porting to xscale architecture board, when check pull range, it returns that it doesn't support pull mode. for example: gst-launch filesrc location=a.mp3 ! myelement ! filesink location=test.dat where myelement is working under pull mode. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Looks like you meant this to go against gstreamer. reassigning.
Which GStreamer core version is that with? Could you attach a debug log please? $ export GST_DEBUG=*:5 $ export GST_DEBUG_NO_COLOR=1 $ gst-launch-0.10 -v filesrc location=test.mp3 ! yourelement ! filesink location=test.dat 2>&1 | gzip > dbg.log.gz
Created attachment 64378 [details] when I don't set debug level to 5
Created attachment 64379 [details] when i set debug level to 5, it cause segmentation falut, log attached
I tred both core 0.10.4 and 0.10.3, all could not work.
(In reply to comment #2) > Which GStreamer core version is that with? 0.10.4 > Could you attach a debug log please? > $ export GST_DEBUG=*:5 > $ export GST_DEBUG_NO_COLOR=1 > $ gst-launch-0.10 -v filesrc location=test.mp3 ! yourelement ! filesink > location=test.dat 2>&1 | gzip > dbg.log.gz when i don't set debug level to 5, as i discribed above but when i do as you said, it caused segmentation fault.
(In reply to comment #6) > when i don't set debug level to 5, as i discribed above > but when i do as you said, it caused segmentation fault. Could you please post a stack trace of where the segmentation fault occurs then? You should use the latest core release (0.10.4, might also be worth trying the 0.10.5 prerelease or CVS HEAD).
You could also try making a debug log with GST_DEBUG=*:4 (instead of *:5), maybe it doesn't crash then.
(In reply to comment #7) > (In reply to comment #6) > > when i don't set debug level to 5, as i discribed above > > but when i do as you said, it caused segmentation fault. > Could you please post a stack trace of where the segmentation fault occurs > then? pgd = c3bc0000 [00000000] *pgd=83700011, *pte=00000000, *ppte=00000000 PC is at 0x404ef128 LR is at 0x4042f00c pc : [<404ef128>] lr : [<4042f00c>] Not tainted sp : befff0f4 ip : 00000000 fp : befff4ec r10: 4046b808 r9 : 00033218 r8 : 00000000 r7 : 0000000f r6 : 00000073 r5 : 00000000 r4 : 0000006c r3 : 000000d8 r2 : befff170 r1 : 00032c48 r0 : fffffff8 Flags: nZcv IRQs on FIQs on Mode USER_32 Segment user Control: 400397F Table: 83BC0018 DAC: 00000015 Segmentation fault > You should use the latest core release (0.10.4, might also be worth trying the > 0.10.5 prerelease or CVS HEAD). I used the latest core release 0.10.4
(In reply to comment #8) > You could also try making a debug log with GST_DEBUG=*:4 (instead of *:5), > maybe it doesn't crash then. GST_DEBUG=*:4, 3,5 all crash
> > Could you please post a stack trace of where the segmentation fault occurs > > then? > > pgd = c3bc0000 > [00000000] *pgd=83700011, *pte=00000000, *ppte=00000000 > PC is at 0x404ef128 > LR is at 0x4042f00c > pc : [<404ef128>] lr : [<4042f00c>] Not tainted > sp : befff0f4 ip : 00000000 fp : befff4ec > r10: 4046b808 r9 : 00033218 r8 : 00000000 > r7 : 0000000f r6 : 00000073 r5 : 00000000 r4 : 0000006c > r3 : 000000d8 r2 : befff170 r1 : 00032c48 r0 : fffffff8 > Flags: nZcv IRQs on FIQs on Mode USER_32 Segment user > Control: 400397F Table: 83BC0018 DAC: 00000015 > Segmentation fault > > You should use the latest core release (0.10.4, might also be worth trying the > > 0.10.5 prerelease or CVS HEAD). > I used the latest core release 0.10.4 Thanks for that, but I'm afraid it's not really that useful to us. By 'stack trace' I mean what gdb prints when you type 'bt' there after a crash. Please see http://live.gnome.org/GettingTraces#gdb-only for more details (assuming gdb works on that platform). It would be best if you compiled GStreamer with debugging symbols for this (ie. pass --enable-debug to ./configure).
Any chance bug #332841 is what's causing the crashes when using GST_DEBUG?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!