[Bug debuginfod/32701] gdb is attempting to write to / and write to rpm's database for no reason.

2025-02-16 Thread nkkra...@uni-sofia.bg
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.

2025-02-16 Thread nkkra...@uni-sofia.bg
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.

2025-02-16 Thread nkkra...@uni-sofia.bg
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.