search for: llvm_pass

...org/D54187#1290282 [1] https://github.com/SNSystems/dexter [2] https://www.youtube.com/watch?v=XRT_GmpGjXE [3] https://llvm.org/devmtg/2018-04/slides/Bedwell-Measuring_the_User_Debugging_Experience.pdf [4] https://github.com/jmorse/dexter/tree/f46f13f778484ed5c6f7bf33b8fc2d4837ff7265/tests/nostdlib/llvm_passes [5] https://github.com/llvm/llvm-project/tree/master/debuginfo-tests -- Thanks, Jeremy

+ 1 to Paul’s suggestions. I’d add that if an open bug report isn’t assigned to anyone, you can assume it’s fair game. Feel free to assign a bug to yourself if you start working on it. To toss another idea out there, you might try picking a small .o and working backwards to figure out why location information in it is incorrect. This can reveal a different set of bugs compared to e.g. running

...reenshot attached. Thanks, Vidya Sagar. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121029/6c34fb72/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: LLVM_PASS.odt Type: application/octet-stream Size: 258637 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121029/6c34fb72/attachment.obj>

Hi llvm-dev@, This is a proposal for LLVM to adopt Sony's Dexter tool [0], import it into the debuginfo-tests repo, and use it to run integration tests between debuggers and clang/llvms debuginfo. (Sony has approved donating Dexter to LLVM). Background ---------- The debuginfo-tests repo contains an integration test suite for debug data, which builds each test case from its source code