You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One question: We did the coverage calculation on the contract side before, and it was a curve to save the country: first compile it into x64 code with x64-simulator, and then directly run it natively to do coverage calculation.
Considering that the debugger can already generate flame graphs, can you consider using the debugger for coverage calculations as well? In this way, the data measured on the contract may be more accurate. In the case of no sanitizer, it may also simplify the things to be done on the contract side (there is no need to maintain the same code to compile multiple environments)
One question: We did the coverage calculation on the contract side before, and it was a curve to save the country: first compile it into x64 code with x64-simulator, and then directly run it natively to do coverage calculation.
Considering that the debugger can already generate flame graphs, can you consider using the debugger for coverage calculations as well? In this way, the data measured on the contract may be more accurate. In the case of no sanitizer, it may also simplify the things to be done on the contract side (there is no need to maintain the same code to compile multiple environments)
中文
提一个问题:之前我们做合约端的 coverage 计算,都是曲线救国的方式:先用 x64-simulator 编译成 x64 代码,然后直接原生跑,来做 coverage 计算。
考虑到现在 debugger 已经能生成火焰图,可不可以考虑同样用 debugger 来进行 coverage 的计算?这样对合约测得的数据可能更准确,在不需要 sanitizer 的情况下,可能也可以简化合约端要做的事情(不需要维护同一份代码编译多个环境了)
The text was updated successfully, but these errors were encountered: