Neither mono's `kill -QUIT $PID` method of writing stacktraces nor gdb's `t a a bt` showed that managed code was running in the main thread. Only LLDB did.
Can we at least fix `kill -QUIT` because we rely on that *a lot* to figure out what our threads are doing. Here is an example threaddump from mono, gdb and lldb where only lldb shows managed code in the main thread.
This is probably caused by the monitor changes, we directly call the monitor_enter () etc. c functions without a wrapper so we can't produce an async stacktrace if they block.
Fixed in mono master c5512c0d3e2b102ed16158ce8c599c8203ccd510 and the mono-4.3.2-branch 9f44a62acf718d91320420c1c77e855a63f3c3f9.
@Alan, @Zoltan : It would be great if you let us know that what and how to reproduce this issue. This issue must be reproduced at our end before verifying it.
Looking for your help!
Its not a product problem, it doesn't need to be verified.
Thanks @Zoltan for the information. I am closing this issue as per comment(4).
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 Links.
Create a new report for Bug 38525 on Developer
Community or GitHub if you have new information to add and do not yet see a matching
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
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.