Dear HN community,
I am one of the paper authors, the paper has been accepted for presentation at ASPLOS 2021.
If you have any question let me know!
I am one of the paper authors, the paper has been accepted for presentation at ASPLOS 2021.
If you have any question let me know!
It'd be great to hunt those kinds of bugs, however it's hard to define what the "right" behaviour would be in those circumstances.
We are able to identify some kind of mis-stepping behaviour (look at Section 7-6). However, as you can imagine, we cannot catch all cases.
As you pointed out, a real problem is that there is no clear definition of what should be the semantic of debug information in the optimized binary (e.g., the compiler is free to squish several lines of source code into a smaller snippet of assembly language).
We are working to have more refined results in the near future .
We plan to use the framework to investigate more the correctness of debug information. Personally, I am not interested in startup and commercial opportunities.
Releasing the software is a step we are discussing.
Is there anybody working on evolving DWARF in the ways you suggest in the paper?
We are not working on DWARF. However, we hope that the paper will spur a public discussion on these problems. Helping the entire community to have a more expressive standard.