Skip to content

Debug information generated for lexical blocks is incorrect. #7819

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
michaelwoerister opened this issue Jul 16, 2013 · 2 comments
Closed

Debug information generated for lexical blocks is incorrect. #7819

michaelwoerister opened this issue Jul 16, 2013 · 2 comments
Labels
A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.)

Comments

@michaelwoerister
Copy link
Member

debuginfo::block() uses the provided trans::common::block for creating lexical block DIEs. trans::common::block, however, corresponds to LLVM basic blocks and not to rust lexical blocks.

A possible direction towards correcting this could be to look at the scope_info field in trans::common::block or to get ahold of the correct ast::blk somehow.

@jdm
Copy link
Contributor

jdm commented Jul 16, 2013

Nice find.

@michaelwoerister
Copy link
Member Author

This turns out to be a false alarm. debuginfo::block_metadata() already searches for the right ast::blk. I added some documentation to make this clear to the currently open PR (#7710).

@bors bors closed this as completed in 8aae6ed Jul 20, 2013
flip1995 pushed a commit to flip1995/rust that referenced this issue Nov 4, 2021
…ncation, r=flip1995

avoid linting `possible_truncation` on bit-reducing operations

---

*Please write a short comment explaining your change (or "none" for internal only changes)*

changelog: avoid linting `possible_truncation` on bit-reducing operations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants