[Mono-bugs] [Bug 79520][Maj] Changed - incorrect binding to gtk_init_check (twice)

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by toshok at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=79520

--- shadow/79520	2006-09-29 11:24:57.000000000 -0400
+++ shadow/79520.tmp.10340	2006-09-29 11:26:10.000000000 -0400
@@ -42,6 +42,14 @@
 it handles that gracefully.
 
 ------- Additional Comments From toshok at ximian.com  2006-09-29 11:24 -------
 both gtk_init_check and gdk_init_check (which we also bind
 incorrectly) can handle NULL argv's, so the IntPtr.Zero change seems
 like the way to go.
+
+------- Additional Comments From toshok at ximian.com  2006-09-29 11:26 -------
+oh, and the reason we likely aren't bitten by any memory corruption is
+that the gtk code continually does things like:
+
+if (argc && argv) { ... do stuff ... }
+
+and we're passing argc as 0.