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 787310 - Runtime error "Error:error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security]"
Runtime error "Error:error: format string is not a string literal (potential...
Status: RESOLVED DUPLICATE of bug 786591
Product: GStreamer
Classification: Platform
Component: dont know
1.x
Other Windows
: Normal blocker
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-09-05 12:44 UTC by Ravi Gupta
Modified: 2017-09-06 08:38 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screen shot for error log in android studio (119.00 KB, image/png)
2017-09-05 12:44 UTC, Ravi Gupta 		Details

Description Ravi Gupta 2017-09-05 12:44:54 UTC 
Created attachment 359182 [details]
screen shot for error log in android studio

Android Studio version :- 2.3.2
Android NDK version :- android-ndk-r15c
Gstremer lib version :- 1.2.2/1.12.2

Please find the screen shot for error log in android studio at runtime.
Comment 1 André Klapper 2017-09-05 12:52:46 UTC 
Could you please explain why this related to GStreamer code at all / steps to reproduce? See https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/Guidelines

Also, please provide error logs as text so it can be searched for. 
The error logs should also offer the exact place where the error happens. 
This is currently missing in this bug report. :)
Comment 2 André Klapper 2017-09-05 19:59:22 UTC 
[ @Maintainers: Potential dup of bug 786591? ]
Comment 3 Sebastian Dröge (slomo) 2017-09-06 08:38:37 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 786591 ***