extremeDB debug说明


 Always use the debug runtime during the development cycle
 Use the release version during the development phase to
measure the performance / CPU utilization of the application
 Install an error handler via the mco_set_error_handler() API
 If the execution is trapped inside the error handler, examine the
application's call stack and find the application's function that
issued the runtime call causing the assertion
 Inspect mco.h file to see why the runtime asserted, e.g. an error
in the transaction manager, heap corruption, a cursor is
corrupted, etc. Check the appropriate application entity just
before the fatal runtime call was issued and make sure that the
entity –transaction handle, object handle or heap - is in fact
corrupted
 Go back through the stack and try to find the application code
where the entity was corrupted.
————————————————
版权声明：本文为CSDN博主「Bruce-Lan」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。
原文链接：https://blog.csdn.net/longlongago7777/article/details/38614931