I've run into a situation where I've seen mono abort due to a failed assertion, and in logcat I was able to see the error message along with the C file/line where the assertion failed, so you definitely get some log help there (at least in what I've seen). I'll be filing a bug with a repro case for mine soon, once I boil it down to a smaller test project.
- Greg On Tue, Jul 26, 2011 at 9:06 AM, Jonathan Pryor <[email protected]> wrote: > On Jul 26, 2011, at 8:30 AM, Wally McClure wrote: > > To add to this, I have also seen issues where something happens in the > try part of the try-catch and nothing is caught. > > The explanation for this is straightforward: the mono runtime aborted. No > exception is thrown for most of mono's abort conditions. > > Eventually, running within the debugger should allow you to get the stack > trace for when mono aborts, but that doesn't help if you're not debugging. > However, it's entirely plausible that mono will log the stack trace/etc. to > `adb logcat`; it would be interesting if someone could verify this. > > As always, if you do get a repro for this, please file a bug. > > - Jon > > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid >
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
