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 92897 - Crash when editing graph
Crash when editing graph
Status: VERIFIED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-editor
git master
Other other
: Normal normal
: 0.4.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-09-10 01:09 UTC by rothwell
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description rothwell 2002-09-10 01:09:45 UTC 
Package: GStreamer
Severity: normal
Version: 0.4.0.1
Synopsis: Crash when editing graph
Bugzilla-Product: GStreamer
Bugzilla-Component: gst-editor
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:

Reconnecting playondemand, between mad and audioscale, gst-editor
crashed.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/gst-editor'

[New Thread 1024 (LWP 1720)]
0x420a0a89 in wait4 () from /lib/i686/libc.so.6

+ Trace 27143

Thread 1 (Thread 1024 (LWP 1720))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #0 wait4
    from /lib/i686/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-09-09 21:09 -------

Unknown version unspecified in product GStreamer. Setting version to "0.3.3".
Reassigning to the default owner of the component, gstreamer-maint@bugzilla.gnome.org.
Comment 1 Thomas Vander Stichele 2002-09-15 16:40:38 UTC 
Could you provide more information ?
examples :
- gdb output from "info threads"
- a bt of the thread that actually segfaulted
- a saved xml pipeline from right before the crash so we can reproduce

thanks
Comment 2 Christian Fredrik Kalager Schaller 2002-11-15 20:24:54 UTC 
As we haven't heard anything back I assume this is fixed in latest
version. Closing.