Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Scary bug. I was getting segfaults when using these unmanaged double byte pointers. Turns out when the method was defined on a generic base class, the JIT compiler completely ignores any indexing of the double byte pointer. Moving the base method to a base class that wasn't generic fixed the problem.
Visual Studio deleted my temp project, so I don't have the mock source I created, but here is the gist:
public void BaseBaseMethod(byte** test)
Console.WriteLine(test); // WRONG this returns same address as test, even test returns the same
class BaseClass : BaseBaseClass<object>
public void BaseMethod(byte** test)
Console.WriteLine(test); // this works
class MyClass : BaseClass
public void MyMethod()
var test= stackalloc byte;
test = (byte*)(IntPtr)0;
test = (byte*)(IntPtr)1;
this.BaseBaseMethod(test); // WRONG bad
this.BaseMethod(test); // works
Please attach a test case which compiles.
If you can still reproduce with latest mono version, please feel free to reopen the bug. Thank you.