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 136793 - segfault in gst-inspect-0.7 version 0.7.6
segfault in gst-inspect-0.7 version 0.7.6
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.7.x
Other Linux
: Normal major
: 0.8.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-10 19:17 UTC by burrelln
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description burrelln 2004-03-10 19:17:33 UTC 
I get a segfault in a newly installed gst-inspect version 0.7.6.  The gdb
output is as follows:

root@qg[/usr/local/portage/media-libs/gst-plugins]# gdb gst-inspect-0.7
GNU gdb 6.0
Copyright 2003 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 "i686-pc-linux-gnu"...Using host libthread_db
library "/lib/libthread_db.so.1".
 
(gdb) run
Starting program: /usr/bin/gst-inspect-0.7
 
Program received signal SIGSEGV, Segmentation fault.
g_str_hash (key=0x0) at gstring.c:76
76      gstring.c: No such file or directory.
        in gstring.c
(gdb) where

+ Trace 44991

  • #0 g_str_hash
    at gstring.c line 76
  • #1 g_hash_table_lookup
    at ghash.c line 192
  • #2 main
    at gst-run.c line 347 






Comment 1


burrelln





          2004-03-10 19:20:04 UTC
        



Bug was caused by a mis-installation of gstreamer.  gst-inpect-0.7
refers to a previously installed version.






Comment 2


David Schleef





          2004-03-10 21:28:59 UTC
        



Can you explain how it happened and/or how to reproduce it?  (e.g.,
which files were where, etc.)  It seems like a simple bug to fix if I
could figure out how it got triggered.






Comment 3


burrelln





          2004-03-10 21:35:03 UTC
        



The problem was with my hacked gentoo ebuild that put the new versions
in gst-inspect-0.8-0.7 rather than gst-inspect-0.7 as I had expected.
 gst-inspect-0.7 was the binary from version 0.7.5.  Does that explain
anything?  I'm thinking a link error/relocation error/basic brokenness
of trying to do things this way.






Comment 4


David Schleef





          2004-03-10 23:51:09 UTC
        



Ok, found it.  thanks for helping.