I don’t think the actual bug has been reported twice, just Alexander already
picked it up (maybe it’s affecting him, too). My colleague opened the bug
report because we updated the mono framework we are certifying against to
3.12.1 and this issue appeared. He said we didn’t have issues with
Found the issue and created PR 1839: https://github.com/mono/mono/pull/1839
Please take a look and let me know if you have any concerns with the fix.
Thanks,
Dave
On May 28, 2015, at 3:51 PM, David Curylo cury...@asme.org wrote:
I’m researching an issue reported by a colleague of mine. The
Hello,
There is already a similar pull request.
The issue is that returning NULL there has a slightly different meaning.
So the complete fix is to restructure some of the code.
https://github.com/mono/mono/pull/1817
Miguel
On Thu, May 28, 2015 at 4:25 PM, David Curylo cury...@asme.org wrote:
Cool. I didn’t see any traffic on the bug report so didn’t know you were
already addressing this. Anything I can do to help move the other PR forward?
On May 28, 2015, at 4:29 PM, Miguel de Icaza mig...@xamarin.com wrote:
Hello,
There is already a similar pull request.
The issue is
I’m researching an issue reported by a colleague of mine. The error is rather
serious as the use of a bad type name causes a native SIGSEGV and kills the
runtime, when it really should just return a null because it can’t find the
type. This code reproduces the issue:
