-
Notifications
You must be signed in to change notification settings - Fork 13.3k
debuginfo: Improvements for stepping experience in GDB #10966
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
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
ae66285
debuginfo: Always set column information to zero for source locations.
michaelwoerister 08bc072
debuginfo: Clear debug source locations at beginning of functions.
michaelwoerister 184d394
debuginfo: Clear source positions where they'd confuse LLVM otherwise.
michaelwoerister 7eae649
debuginfo: Create separate lexical block for function bodies.
michaelwoerister 45e472a
debuginfo: Get rid of redundant argument copying with debuginfo activ…
michaelwoerister 69f4bf7
debuginfo: Use same behavior as Clang for calculating scope_line para…
michaelwoerister b0100c5
debuginfo: Set the is_local_to_unit attribute of functions correctly
michaelwoerister 91efb2a
debuginfo: Set correct source position for function calls.
michaelwoerister 89b47d5
debuginfo: Add test cases for function prologue handling.
michaelwoerister d35fff8
debuginfo: Added some documentation of source location management.
michaelwoerister 9384de7
debuginfo: Add comment on is_local_to_unit parameter.
michaelwoerister File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the key piece that makes sure we handle the
__morestack
prelude correctly? It's probably worth expanding this comment to cover why we need to handle this specially (and at least a mention of__morestack
so that there is no ambiguity about what "function prelude" means).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me if you add comments
On Sat, Dec 14, 2013 at 7:56 AM, Huon Wilson [email protected]:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's necessary for any kind of function, with and without segmented stack. It's probably best if I add a section about function prologues and line information at the beginning of the file, since the functionality spans across multiple functions here...
But it's definitely a good idea to add a bit of explanation on these topics. Thanks for you suggestions, Huon!