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

[nkkralev@uni-sofia.bg]

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

PlaceholderName <nkkralev@uni-sofia.bg> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|NOTABUG                     |FIXED

--- Comment #9 from PlaceholderName <nkkralev@uni-sofia.bg> ---
(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.