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 770392 - Always get "GLib-GObject-WARNING **: attempt to override closure->va_marshal [...] with new marshal" when compiling with GTK+ (or gtkmm, etc.) on Windows (MSYS2/MinGW)
Always get "GLib-GObject-WARNING **: attempt to override closure->va_marshal ...
Status: RESOLVED DUPLICATE of bug 769076
Product: gtk+
Classification: Platform
Component: Backend: Win32
3.20.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-08-25 13:39 UTC by Daniel Boles
Modified: 2016-10-27 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Boles 2016-08-25 13:39:25 UTC
Whenever we run a program compiled with GTK+ on MSYS2 and MinGW/GCC - and possibly other build environments, I dunno - a message of the following form is given at exit:

> (a.exe:4744): GLib-GObject-WARNING **: attempt to override closure->va_marshal (0000000063a48a20) with new marshal (0000000066710f98)


I am far from the only person who has noticed and been worried by this; here are just a few other examples:

 * https://mail.gnome.org/archives/vala-list/2016-June/msg00064.html
 * https://mail.gnome.org/archives/gtkmm-list/2016-August/msg00023.html
 * http://forum.gtkd.org/groups/GtkD/thread/459/


We can see that the error is coded in gobject/gclosure.c:
> https://git.gnome.org/browse/glib/tree/gobject/gclosure.c#n899


Mercifully, there don't appear to be any other problems (other than resources needing copied into the output exe's folder, etc.). But is this something that needs fixed?


I must stress this is literally the only 'problem' I have with GTK+/gtkmm stuff in MSYS2 - given how easy MSYS2 makes it and how GDK Win32 just works effortlessly. My programs look and function exactly on Win32 as in my main development on GNOME (and AFAIK my even lesser tested OS X) - so I'm hugely grateful to everyone who's made cross-platform development as trivial as this!


HTH and thanks in advance.
Comment 1 Ignacio Casal Quinteiro (nacho) 2016-08-25 13:49:01 UTC
I think is is already fixed by Matthias...
Comment 2 LRN 2016-08-25 13:51:21 UTC

*** This bug has been marked as a duplicate of bug 769076 ***
Comment 3 Daniel Boles 2016-08-25 14:10:55 UTC
Oops, thanks both! Has the fix been committed? I can't seem to find it.
Comment 4 Daniel Boles 2016-08-25 14:11:59 UTC
P.S. I swear I did search before posting O:-) but Bugzilla didn't show me anything, probably because I included the debug log preamble, unlike that dupe
Comment 5 Daniel Boles 2016-10-27 12:31:34 UTC

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