<div dir="ltr">Yeah, so the reason I was asking about the nature g_assert being compiled out is the following from the documentation: <a href="https://developer.gnome.org/glib/stable/glib-Testing.html#g-assert">https://developer.gnome.org/glib/stable/glib-Testing.html#g-assert</a> The macro can be turned off in final releases of code by defining <code class="gmail-literal" style="font-size:14px;margin:0px;padding:1px;border:0px;vertical-align:baseline;background:rgba(0,0,0,0.1)">G_DISABLE_ASSERT</code> when compiling the application, so code must not depend on any side effects from <code style="margin:0px;padding:1px;border:0px;vertical-align:baseline;background:rgba(0,0,0,0.1)">expr</code> . Similarly, it must not be used in unit tests, otherwise the unit tests will be ineffective if compiled with <code class="gmail-literal" style="font-size:14px;margin:0px;padding:1px;border:0px;vertical-align:baseline;background:rgba(0,0,0,0.1)">G_DISABLE_ASSERT</code>. Use <a class="gmail-link" href="https://developer.gnome.org/glib/stable/glib-Testing.html#g-assert-true" title="g_assert_true()" style="font-size:14px;text-decoration-line:none;color:rgb(93,57,110);margin:0px;padding:0px;border:0px;vertical-align:baseline;background:transparent"><code class="gmail-function" style="margin:0px;padding:1px;border:0px;vertical-align:baseline;background:rgba(0,0,0,0.1)">g_assert_true()</code></a> and related macros in unit tests instead. I knew that compiling it out was something that could be done, and I just wanted to make sure that the code I was using was indeed built as it was intended. I'll try updating and see if it goes away. Thanks. <div class="gmail-refsect3" style="margin:0px;padding:0px;border:0px;font-size:14px;vertical-align:baseline;background:transparent"><a name="g-assert.parameters" style="color:rgb(32,74,135);margin:0px;padding:0px;border:0px;vertical-align:baseline;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;font-family:Verdana,Arial,sans-serif"></a> </div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 1, 2019 at 2:11 PM Sebastian Dröge <<a href="mailto:sebastian@centricular.com">sebastian@centricular.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, 2019-10-01 at 11:24 -0500, Ben Rush wrote: > I might be missing something fundamental with respect to the use of > g_assert, but it looks as though it's something intended to be built > out of production or "release" code, right? Assertions are also in release code. If they're hit then the internal state of the code is so wrong that there's no reasonable way forward. Just compiling them out would cause potentially worse problems :) > I ask because I've been encountering (on Windows) a number of > strange, sudden program "crashes" which, upon adding some program- > wide exception trapping code to my server, seems to actually be > assert statements executing and taking down the host process. For > example, I was notified of an RTSP server in production going down > and upon looking at the logs, I see that my trap code generated this > stack trace: > > at 0x7ff93969c902, with code 80000003 in module > C:\Windows\System32\KERNELBASE.dll, stack: > ?????, DebugBreak:?????? > d:\projects\cerbero\autotools\master\build\sources\windows_x86_64\gli > b-2.56.1\glib\gutils.c, g_abort:2566 > d:\projects\cerbero\autotools\master\build\sources\windows_x86_64\gli > b-2.56.1\glib\gtestutils.c, g_assertion_message:2533 > d:\projects\cerbero\autotools\master\build\sources\windows_x86_64\gli > b-2.56.1\glib\gtestutils.c, g_assertion_message_expr:2556 > d:\projects\cerbero\autotools\master\build\sources\windows_x86_64\gst > -plugins-base-1.0-1.15.2\gst-libs\gst\rtsp\gstrtspconnection.c, > gst_rtsp_source_dispatch_write:3899 This problem should be fixed already, it looks very similar to one of the issues that were fixed in the last months. You're using a rather old development version of GStreamer (odd minor version number: 15). Please try again with 1.16.1, and if the problem still exists please create an issue in gitlab. Thanks! -- Sebastian Dröge, Centricular Ltd · <a href="https://www.centricular.com" rel="noreferrer" target="_blank">https://www.centricular.com</a> _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a></blockquote></div>