I have the same problem as reported here:
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.47.el6_2.9.i686 libgcc-4.4.6-3.el6.i686 libstdc++-4.4.6-3.el6.i686
However, I am not the root user so I can't just run debuginfo-install ...
. I was wondering if there's a relatively easy way for me to get these libraries and add a Path to them in my home directory without using a root account.
It cannot create and delete users, modify programs installed as root (which includes anything installed by the package manager, such as LibreOffice), or alter the system at a deep level. I've heard of su.
Run a devcontainer based on local docker-compose.yml I think an easy fix is to run the docker exec commands always with --user root regardless of which user is used for development (configured in docker-compose.yml ). @Rots Actually these are intended to all go into the non-root user's home folder.
An admin could even enable the root account and log in. If you abstract a user account as a combination of mechanistic and conscious actions, human users have both and non-human users including root act purely mechanistically. If you understand how it all works, then if your analogy reinforces that, great!
It looks like non-root user is more secure than admin user. You are an administrator, but not root. The root user can do anything. Administrators can perform actions as root, but ordinarily what administrators do is not done by root. That way, you have full control over your own system, but only when you choose to use it.
There is a way, though I'm not sure I would call it easy. The essential idea is to install the files in your $HOME
and then tell gdb how to find them.
The steps are like:
$HOME
. Sometimes you can do this with rpm -i --prefix=...
, though I don't know if that will work for debuginfo RPMs. You can always extract the files from an RPM using cpio
. Be sure to preserve the directory names.set debug-file-directory
to tell gdb to look at your new directory. You can put multiple directories here by separating them with ;
.Some more fiddling with source directories (see dir
) might be needed after this.
It's maybe worth noting that you normally don't actually need system debuginfo.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With