PLSysSec / sys

Sys: A Static/Symbolic Tool for Finding Good Bugs in Good (Browser) Code

Home Page:https://cseweb.ucsd.edu/~dstefan/pubs/brown:2020:sys.pdf

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Map LLVM bug paths back to source

deian opened this issue · comments

I will look into it when I have time:

This could be helpful:
github.com/avast/retdec

Or

https://llvm.org/docs/SourceLevelDebugging.html

@deian and others: have you make some thoughts how to achieve llvm mapping to code?

For both I can assume you have to disable compiler optimizations and for second compile with debug symbols (-g). Llvm seems to store this info in ll file (debug metadata with lines & column info). Still digesting how to get the corresponsing code source locations.

I can assume you can get last path item from bug path and point to code?