-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[lldb][Progress] Separate title and details #77547
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
chelcassanova
merged 6 commits into
llvm:main
from
chelcassanova:separate-title-and-details
Jan 16, 2024
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
44a3cdc
[lldb][Progress] Separate title and details
chelcassanova 75de25c
fixup! [lldb][Progress] Separate title and details
chelcassanova 8d7c2bf
Update ELF progress report, remove Apple DWARF report, use std::optional
chelcassanova c406acc
Use std::optional for detail update, remove std::optional as member
chelcassanova 16996a8
Use std::move when updating m_details
chelcassanova 3c2b8f7
Fix comment
chelcassanova 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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -519,8 +519,6 @@ void SymbolFileDWARF::InitializeObject() { | |
|
||
if (apple_names.GetByteSize() > 0 || apple_namespaces.GetByteSize() > 0 || | ||
apple_types.GetByteSize() > 0 || apple_objc.GetByteSize() > 0) { | ||
Progress progress(llvm::formatv("Loading Apple DWARF index for {0}", | ||
module_desc.GetData())); | ||
m_index = AppleDWARFIndex::Create( | ||
*GetObjectFile()->GetModule(), apple_names, apple_namespaces, | ||
apple_types, apple_objc, m_context.getOrLoadStrData()); | ||
|
@@ -532,8 +530,7 @@ void SymbolFileDWARF::InitializeObject() { | |
DWARFDataExtractor debug_names; | ||
LoadSectionData(eSectionTypeDWARFDebugNames, debug_names); | ||
if (debug_names.GetByteSize() > 0) { | ||
Progress progress( | ||
llvm::formatv("Loading DWARF5 index for {0}", module_desc.GetData())); | ||
Progress progress("Loading DWARF5 index", module_desc.GetData()); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. DWARF5 on the other hand usually has a single .debug_names table per compile unit, and there can be mixed DWARF5 .debug_names tables along with some compile units that need to be manually indexed, so it might be worth keeping this progress. |
||
llvm::Expected<std::unique_ptr<DebugNamesDWARFIndex>> index_or = | ||
DebugNamesDWARFIndex::Create(*GetObjectFile()->GetModule(), | ||
debug_names, | ||
|
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
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.
updated_detail
is still kept as an empty string by default, though I'm unsure if the empty string orstd::nullopt
is preferred here