After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 347204 - segmentation fault when 'gst-launch fakesrc ! fakesink'
segmentation fault when 'gst-launch fakesrc ! fakesink'
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.6
Other All
: Normal critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-11 09:11 UTC by yuanhui
Modified: 2006-08-09 08:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description yuanhui 2006-07-11 09:11:27 UTC
Steps to reproduce:
1. port gstreamer-0.10.6 to arm
2. gst-launch fakesrc num-buffers=3 ! fakesink
3. 


Stack trace:
/usr/lib $ gst-inspect
coreindexers:  memindex: A index that stores entries in memory
coreelements:  typefind: TypeFind
coreelements:  tee: Tee pipe fitting
coreelements:  filesink: File Sink
coreelements:  queue: Queue
coreelements:  identity: Identity
coreelements:  filesrc: File Source
coreelements:  f禟r[?Filedescriptor Sink
coreelements:  fdsrc: Disk Source
coreelements:  fakesink: Fake Sink
coreelements:  fakesrc: Fake Source
coreelements:  capsfilter: CapsFilter
staticelements:  bin: Generic bin
staticelements:  pipeline: Pipeline object

Total plugins: 3
Total features: 14

/usr/lib $ gst-launch fakesrc num-buffers=3 ! fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Killed

/usr/lib $ gst-launch fakesrc num-buffers=3 ! fakesink --gst-debug=4

[snip]......
DEBUG (0x192d8 - 0:00:03.299994000)         GST_PIPELINE(  167) parse.l(142):_gs
t_parse_yylex: flex: SPACE: [ ]
DEBUG (0x192d8 - 0:00:03.299997000)         GST_PIPELINE(  167) ./grammar.y(846)
:_gst_parse_launch: got 2 elements and 1 links
DEBUG (0x192d8 - 0:00:03.300000000)   GST_PLUGIN_LOADING(  167) gstpluginfeature
.c(108):gst_plugin_feature_load: loading plugin for feature 0x36e30; 'pipeline'
INFO  (0x192d8 - 0:00:03.659994000)  GST_ELEMENT_FACTORY(  167) gstelementfactor
y.c(365):gst_element_factory_create: creating element "pipeline"
DEBUG (0x192d8 - 0:00:03.669992000)              GST_BUS(  167) gstbus.c(222):gs
t_bus_init:<GstBus@0x45990> created
DEBUG (0x192d8 - 0:00:03.669996000)              GST_BUS(  167) gstbus.c(294):gs
t_bus_new:<bus0> created new bus
Segmentation fault

/usr/lib $ gdb gst-launch
GNU gdb 6.3.50.20051114-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "arm-linux"...Using host libthread_db library "/lib/l
ibthread_db.so.1".

(gdb) set args fakesrc num-buffers=3 ! fakesink
(gdb) rum
Undefined command: "rum".  Try "help".
(gdb) run
Starting program: /usr/bin/gst-launch fakesrc num-buffers=3 ! fakesink
Setting pipeline to PAUSED ...

Program received signal SIG32, Real-time event 32.
0x401c22bc in __check_rhosts_file () from /lib/libc.so.6
(gdb) bt
  • #0 __check_rhosts_file
    from /lib/libc.so.6
  • #1 ??
    from /lib/libc.so.6
(gdb) quit
The program is running.  Exit anyway? (y or n) y
/usr/lib $

Other information:
/usr/lib $ gst-launch pipeline
Setting pipeline to PAUSED ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

Caught interrupt --
/usr/lib $
Comment 1 Vincent Untz 2006-08-04 10:35:08 UTC
Moving to gstreamer.
Comment 2 Jan Schmidt 2006-08-04 10:50:28 UTC
Impossible to tell what the problem is from this information. I'd say it's a compilation/build issue, since GStreamer definitely does run on ARM - we've got cross-compiles working on several different ARM cores.
Comment 3 Tim-Philipp Müller 2006-08-04 10:51:36 UTC
SIG32 is a real-time signal. Please type this into gdb (or put it into ~/.gdbinit) before running gst-launch-0.10 in gdb:

 handle SIG32 nostop noprint pass
 handle SIG33 nostop noprint pass

and then reproduce the problem and get a proper stack trace from where it crashes (SIGSEGV).


Also, please use

 $ gdb gst-launch-0.10

(with just 'gst-launch' it will probably not work right)

Thanks.
Comment 4 Tim-Philipp Müller 2006-08-09 08:58:00 UTC
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!