Open Psercom opened 5 years ago
UPDATE: A debugging dll would be a very useful time saver, but we proceeded to debug by binary code exclusion and found, amazingly, that two places in our code where we had two assignments per line (e.g. var1 = var2 = var3; ) resulted separately in mono errors. This seems a mono bug perhaps but illustrates difficulties that are hard to identify without debug support. Thanks for considering.
There seems a barrier to general use for this wonderful and ingenious archtecture and implementation.
We too hit the assertion others are experiencing: DEBUGGING ENABLED* Assertion at /Users/builder/jenkins/workspace/test-mono-mainline-webassembly/label/highsierra/mono/metadata/class-init.c:4108, condition `klass' not met Build with -s ASSERTIONS=1 for more info.
There seems evidence that when applications are built involving more complexity than the very simple demos that a mono-related assertion occurs. See for example issue 181 199 and our own experience trying a dynamic page application.
These seem a show-stopper to general use and it is not clear how to set up debugging to get information as to which features have triggered the assertion.
It could be a win to address this early so as to enable much more general use of a brilliant invention. Thanks for creating it.