Solve the problem of no debugging symbols in high versions of glibc about glibc-all-in-one HOT 9 OPEN

@b0ldfrev Many thanks. It will be great if you create a pull request and become a contributer.

from glibc-all-in-one.

As for the problem of GDB, maybe you can write it down in the README within your PR?

from glibc-all-in-one.

@b0ldfrev Many thanks. It will be great if you create a pull request and become a contributer.

ok , i will do this.

from glibc-all-in-one.

#18 it may not be a good idea to copy '.build-id' to '/usr/lib/debug/.build-id/'，since it corrupts the system debug symbols. as you point out, just updating gdb can solve the problem?

from glibc-all-in-one.

#18 it may not be a good idea to copy '.build-id' to '/usr/lib/debug/.build-id/'，since it corrupts the system debug symbols. as you point out, just updating gdb can solve the problem?

Copying .build-id to the system directory will not overwrite the original system debug symbols, because the version id are completely different. If there are two symbol files with the same name, that means that the two files and symbols are consistent.
In fact, GDB can " set debug-file-directory" to specify the symbol directory, but this can only be loaded when the program is initialized, and will not work when the attached process is debugged.

from glibc-all-in-one.

your solution is correct. however, for security reasons, i don't want others to use my tool under root previledge only. can you provide a solution to let users decide? maybe add a command line option?

from glibc-all-in-one.

your solution is correct. however, for security reasons, i don't want others to use my tool under root previledge only. can you provide a solution to let users decide? maybe add a command line option?

Do you mean to add a Usage to the download program to illustrate the situation?

from glibc-all-in-one.

correct. for eample: ./download glibc-2.23 --system

from glibc-all-in-one.

thanks,it's working

from glibc-all-in-one.