Can you provide with a test case that shows this behavior? If so, please file a bug report.
On Fri, May 2, 2014 at 7:17 AM, Giuliano Barberi <[email protected]>wrote: > Hey guys I'm seeing something strange. It could totally be user error but > I can't seem to figure it out. > > I am doing this on some tasks that I never await in order to get the > exception: > public static Task CatchUnhandledException(this Task task) > { > return task.ContinueWith(continuation => > > Engine.UnhandledExceptionHandler(continuation.Exception), > TaskContinuationOptions.ExecuteSynchronously > | TaskContinuationOptions.OnlyOnFaulted); > } > > and the Engine.UnhandledExceptionHandler just logs the exception. > > What's strange is that the exception is null and also doing > an Environment.StackTrace in the handler also yields nothing. I do have > --debug with the mdb files so I would suspect to get the full stacktrace. I > never saw this issue when I was running on .NET runtime but I also have > added more async code since so I'm not sure if it's something with Mono or > my app. I just can't find anything online and the documentation for Tasks > says that if it's faulted state there will be an exception. > > Regards > -- > Giuliano Barberi > > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list > >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
