[Mono-bugs] [Bug 680190] New: PtrToStructure not working correctly (Specifically with FreeType)
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Wed Mar 16 11:45:34 EDT 2011
https://bugzilla.novell.com/show_bug.cgi?id=680190
https://bugzilla.novell.com/show_bug.cgi?id=680190#c0
Summary: PtrToStructure not working correctly (Specifically
with FreeType)
Classification: Mono
Product: Mono: Runtime
Version: 2.10.x
Platform: 64bit
OS/Version: Ubuntu
Status: NEW
Severity: Major
Priority: P5 - None
Component: interop
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: jonathan.dickinson at k2.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.16
(KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Attempting to use Axiom3D 0.8.0.0 engine on Mono. After getting it to build I
ran into problems with some FreeType interop code; the same code works on the
Microsoft CLR.
The exception is a ObjectReferenceException (due to an access violation).
However, the pointer is retrieved from a previous call to PtrToStructure.
Reproducible: Always
Steps to Reproduce:
1. Extract the files (cuckoo is used as a testing font).
2. gmcs Main.cs
3. mono Main.exe
Actual Results:
ObjectReferenceException due to an invalid pointer (which happens to be well
within the range of the kernel protected address space).
Expected Results:
Successfully marshal the pointer to a FT_GlyphSlotRec.
Ubuntu 10.10 with Mono 2.10.1 x64 (Parallel environment).
I tried to pin down the problem for you; but I am not getting anywhere as I am
completely unfamiliar with how Mono interop works under the covers.
I have triple-verified the code and it looks correct based on the FT tutorials
(C++ ones).
I have spent about 5 days (in total) trying to get you guys more information
but I really am coming up with nothing. There has been no repro attempt using
Mono on Windows.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list