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 158163 - [api] Problem querying on ghostpads
[api] Problem querying on ghostpads
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.8.7
Other Linux
: Normal normal
: 0.8.8
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-13 12:51 UTC by Edward Hervey
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Edward Hervey 2004-11-13 12:51:49 UTC 
When I use a decodebin, querying on one of the pads created (ghostpads)
segfaults with the following :

GLib-GObject-WARNING **: invalid cast from `GstDecodeBin' to `GstAviDemux'

+ Trace 51919

  • #0 gst_avi_demux_get_type
  • #1 gst_pad_query
    from /usr/lib/libgstreamer-0.8.so.1
  • #2 establish_length
    at pitivi-sourcefile.c line 107
  • #3 pitivi_sourcefile_create_mainpipeline
    at pitivi-sourcefile.c line 244 

If I do the same thing but use GST_PAD_REALIZE(pad) as the parameter to
gst_pad_query() it works fine.

Might want to check the gst_pad_query code to see if the ghostpads are
"realized" before queried.

Using gst-plugins-0.8.5
Comment 1 Ronald Bultje 2004-12-16 23:46:02 UTC 
OK, I checked convert/send_event, they dispatch properly with the correct pad as
argument. Query uses the same code, but does the query on the ghostpad (even
though it requests the realpad). While doing that, it casts the provided pad to
a GstPad (which the provided pad already is, but the realized pad isn't)
explicitely, which makes me think that was a typo and not intentional. Fixed in CVS.