[Bug debugedit/33823] debugedit fails to detect sources if DWARF contains relative, not absolute paths (empty debugsourcefiles.list)

[mark at klomp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=33823

--- Comment #11 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #7)
> (In reply to David Abdurachmanov from comment #6)
> > Latest Rust build ( rust-1.95.0-1.fc44 ) failed too. Compared 1.94 vs 1.95 I
> > see that there was "-fdebug-prefix-map=" used.
> > 
> > CFLAGS_riscv64gc_unknown_linux_gnu="-fdebug-prefix-map=/builddir/build/BUILD/
> > rust-1.95.0-build/rustc-1.95.0-src=/rustc/
> > 59807616e1fa2540724bfbac14d7976d7e4a3860" 
> > 
> > CXXFLAGS_riscv64gc_unknown_linux_gnu="-fdebug-prefix-map=/builddir/build/
> > BUILD/rust-1.95.0-build/rustc-1.95.0-src=/rustc/
> > 59807616e1fa2540724bfbac14d7976d7e4a3860"
> > 
> > [..]
> > error: Empty %files file
> > /builddir/build/BUILD/rust-1.95.0-build/rustc-1.95.0-src/debugsourcefiles.
> > list
> > RPM build errors:
> >     Empty %files file
> > /builddir/build/BUILD/rust-1.95.0-build/rustc-1.95.0-src/debugsourcefiles.
> > list
> 
> yeah, don't do that. You are remapping file names to a "weird" (unexisting)
> location. There is no way for debugedit to guess what you are meaning here.
> Unless you explicitly tell debugedit about that new location it cannot find
> any files.

So I think this issue really isn't what this bug report is about. This bug
report is about having "relative" source paths, which aren't handled by
debugedit atm. This specific issue is about non-existing absolute source paths
in the DWARF data. Which seems a specific Rust issue. And it looks like Fedora
at least is reverting this using --set rust.remap-debuginfo=false
https://src.fedoraproject.org/rpms/rust/c/1915d3f355de773f8e1eae5f5c0c7dce43b53575?branch=rawhide

-- 
You are receiving this mail because:
You are on the CC list for the bug.