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 756490 - gleffects : crashes on Windows/MinGW
gleffects : crashes on Windows/MinGW
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Windows
: High critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-13 10:13 UTC by Philippe Renon
Modified: 2016-05-22 20:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Philippe Renon 2015-10-13 10:13:52 UTC 
Following pipeline crashes on current master with gstreamer compiled under Windows/MinGW.

gst-launch-1.0.exe videotestsrc ! glupload ! gleffects ! gldownload ! videoconvert ! d3dvideosink

This pipeline works fine:

gst-launch-1.0.exe videotestsrc ! glupload ! gldownload ! videoconvert ! d3dvideosink

I obtained a bt of the crash but it was not very informative.
I did not capture it but it went along those line:
- crash in nvogl.dll (nvidia driver)
- ?
- ?
- ?
Comment 1 Matthew Waters (ystreet00) 2015-10-15 06:20:53 UTC 
That's not really all that useful of a backtrace :)  Could you get debugging symbols for the gstreamer modules (specifically gst-plugins-bad) and get a new backtrace?
Comment 2 Sebastian Dröge (slomo) 2015-10-15 06:39:03 UTC 
You already have debug symbols on Windows, but you need to use gdb for creating the backtrace instead of the VS debugger.
Comment 3 Philippe Renon 2015-10-15 07:00:18 UTC 
I am using MinGW and did use gdb.

How do I get debug symbols when building with cerbero/MinGW ?
Comment 4 Sebastian Dröge (slomo) 2015-10-15 07:01:36 UTC 
You already have them. Can you paste the complete backtrace as given by gdb?
Comment 5 Tim-Philipp Müller 2016-05-22 20:48:47 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!