[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701 Frank Ch. Eigler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #4 from Frank Ch. Eigler --- . -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701 Frank Ch. Eigler changed: What|Removed |Added Resolution|FIXED |NOTABUG --- Comment #10 from Frank Ch. Eigler --- > Meaning that, the choice of how to react when an environment variable is > missing is a decision made by the program, it can report and error or > it can use an empty string and proceed or it can use some default like > "/" and proceed. I suppose so. The latter is fine too. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701 Tom de Vries changed: What|Removed |Added CC||elfutils-devel at sourceware dot o ||rg, vries at gcc dot gnu.org Version|10.1|unspecified Component|gdb |debuginfod Product|gdb |elfutils --- Comment #2 from Tom de Vries --- I think this is related to the make_cache_path function in debuginfod/debuginfod-client.c in elfutils. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701 Frank Ch. Eigler changed: What|Removed |Added CC||fche at redhat dot com --- Comment #3 from Frank Ch. Eigler --- An environment that has no $HOME nor $XDG_CACHE_HOME set is unusual enough not to warrant error messages even better than what gdb already printed (EPERM). GDB is probably attempting to access the RPM database so it can suggest debuginfo RPMs to install, given that its debuginfod-based attempts failed. I don't see any bug here. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701 PlaceholderName changed: What|Removed |Added Resolution|NOTABUG |FIXED --- Comment #5 from PlaceholderName --- (In reply to Tom de Vries from comment #2) > I think this is related to the make_cache_path function in > debuginfod/debuginfod-client.c in elfutils. Yes, it looks like this here is the culprit that decided to use "/" as a default in case $HOME doesn't exist https://github.com/sourceware-org/elfutils/blob/master/debuginfod/debuginfod-client.c#L1015 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701 --- Comment #6 from PlaceholderName --- (In reply to Frank Ch. Eigler from comment #3) > An environment that has no $HOME nor $XDG_CACHE_HOME set is unusual enough > not to warrant error messages even better than what gdb already printed > (EPERM). > I don't see any bug here. Are there any other programs from https://sourceware.org which say if "$HOME" is not defined, use "/" ? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701
PlaceholderName changed:
What|Removed |Added
Resolution|NOTABUG |FIXED
--- Comment #9 from PlaceholderName ---
(In reply to Frank Ch. Eigler from comment #7)
> It is normal to build paths like getenv("HOME") + "/" + str(something),
> so if $HOME is unset, you still get a "/" to start with.
...and when I ask bash to do this:
$ env - bash -c 'set -u ; echo $HOME' ; echo "command finished with exit code
$?"
The result is:
bash: line 1: HOME: unbound variable
command finished with exit code 127
Meaning that, the choice of how to react when an environment variable is
missing is a decision made by the program, it can report and error or it can
use an empty string and proceed or it can use some default like "/" and
proceed.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701
--- Comment #7 from Frank Ch. Eigler ---
It is normal to build paths like getenv("HOME") + "/" + str(something),
so if $HOME is unset, you still get a "/" to start with.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.
https://sourceware.org/bugzilla/show_bug.cgi?id=32701 Tom de Vries changed: What|Removed |Added Resolution|FIXED |NOTABUG --- Comment #8 from Tom de Vries --- Reverting to resolved-notabug, assuming the resolved-fixed was an accident. -- You are receiving this mail because: You are on the CC list for the bug.
