Set path of the compile unit to the source directory
As part of the effort to implement split dwarf debug info, we ended up setting the compile unit location to the output directory rather than the source directory. Furthermore, it seems like we failed to remap the prefixes for this as well! The desired behaviour is to instead set the `DW_AT_GNU_dwo_name` to a path relative to compiler's working directory. This still allows debuggers to find the split dwarf files, while not changing the behaviour of the code that is compiling with regular debug info, and not changing the compiler's behaviour with regards to reproducibility. Fixes #82074
This commit is contained in:
parent
3158857297
commit
16c71886c9
4 changed files with 13 additions and 21 deletions
|
@ -667,17 +667,6 @@ impl OutputFilenames {
|
|||
path
|
||||
}
|
||||
|
||||
/// Returns the name of the Split DWARF file - this can differ depending on which Split DWARF
|
||||
/// mode is being used, which is the logic that this function is intended to encapsulate.
|
||||
pub fn split_dwarf_filename(
|
||||
&self,
|
||||
split_debuginfo_kind: SplitDebuginfo,
|
||||
cgu_name: Option<&str>,
|
||||
) -> Option<PathBuf> {
|
||||
self.split_dwarf_path(split_debuginfo_kind, cgu_name)
|
||||
.map(|path| path.strip_prefix(&self.out_directory).unwrap_or(&path).to_path_buf())
|
||||
}
|
||||
|
||||
/// Returns the path for the Split DWARF file - this can differ depending on which Split DWARF
|
||||
/// mode is being used, which is the logic that this function is intended to encapsulate.
|
||||
pub fn split_dwarf_path(
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue