Use the path of the original file to find the debuglink destination

[zecakeh]

As defined in https://www-zeuthen.desy.de/unix/unixguide/infohtml/gdb/Separate-Debug-Files.html:

For the “debug link” method, gdb looks up the named file in the directory of the executable file, then in a subdirectory of that directory named .debug, and finally under the global debug directory, in a subdirectory whose name is identical to the leading directories of the executable's absolute file name.

The paths were hardcoded by using the directories provided in the examples, which might not work, especially if the app is not installed via a package.

I'm not 100% sure of the assumptions I made to get the original file location as a Path.

Note that in the three cases it uses an absolute path but it might be enough to use a relative path for the two first locations.

Fixes #37 for me.

[mstange]

Looks good, thank you for fixing this!

[mstange]

I'm not 100% sure of the assumptions I made to get the original file location as a Path.

Note that in the three cases it uses an absolute path but it might be enough to use a relative path for the two first locations.

I think what you have is fine.