[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 #9 from Mark Wielaard <mark at klomp dot org> ---
(In reply to David Abdurachmanov from comment #8)
> Shouldn't we make debugedit fail in this case?

But how do we know it "failed"?
You asked it for a list of files starting with a certain prefix in the (debug)
file.
It didn't find any with that prefix. Is that a failure or are there just not
any such files?

> We are failing on riscv64 because of a different issue. On non-riscv64 arch
> (e.g. x86_64, aarch64, etc.) you get a directory and it's get packaged. On
> riscv64 we don't get directory reported by debugedit and thus
> debugsourcefiles.list is empty causing RPM to fail it.

Which directory/path is this?

> If debugedit cannot handle it should fail with an error.

But we have to figure out what "it" is.
This bug is about debugedit not handling "relative" paths (as if you used
-fdebug-prefix-map=$(pwd)=.
But "this" seems to be something else.

> Again, we also need to debug why debugedit provides different output on
> riscv64.

Do you happen to have a x86_64 and riscv64 file that show this?

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