[Mono-bugs] [Bug 78721][Nor] Changed - GdipGetLogFont[A|W] don't initialize the LOGFONT (Out)

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Jun 28 13:11:29 EDT 2006

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 sebastien at ximian.com.


--- shadow/78721	2006-06-28 12:43:40.000000000 -0400
+++ shadow/78721.tmp.25076	2006-06-28 13:11:29.000000000 -0400
@@ -1,23 +1,23 @@
 Bug#: 78721
-Product: Mono: Runtime
+Product: Mono: Class Libraries
 Version: 1.0
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: NOTABUG
+Status: REOPENED   
 Severity: Unknown
 Priority: Normal
-Component: interop
+Component: libgdiplus
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: sebastien at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
-Summary: marshaling bug with LOGFONT (mono_marshal_free_asany)
+Summary: GdipGetLogFont[A|W] don't initialize the LOGFONT (Out)
 Description of Problem:
 When freeing a LOGFONT mono_marshal_free_asany allocates a new string (not
 sure why) which can be invalid (and get trapped by valgrind).
 Steps to reproduce the problem:
@@ -107,6 +107,9 @@
 * If I zeroize the string (in GdipGetLogFontA) then the error doesn't
 occurs. However I don't think this should be required (at least not in
 ------- Additional Comments From vargaz at gmail.com  2006-06-28 12:43 -------
+------- Additional Comments From sebastien at ximian.com  2006-06-28 13:11 -------
+Oops, wasn't a marshaling bug (but it's still a bug ;-)

More information about the mono-bugs mailing list