Use this document to comment and answer the questions from
Solidity debugging symbols: requirements gathering
Please do:
Yes. When generating Solidity stack traces we found that lots of reverts come from unmapped sections of the bytecode. It's not always clear what to do in those cases.
We developed some heuristics to try and identify most of the error conditions, but they are really fragile.
I understand that sometimes these unmapped sections come from the implementation of the Solidity runtime, but that's not always the case. For example, this issue describes how in Solidity 0.6.3+ some reverts()
coming from the user are sometimes unmapped.