For probes like `process("PATH").begin` and `process("PATH").function`, when we use symlinks for PATH, the task finder would silently fail to match the target processes' procname. We should always resolve PATH at runtime to the real file path. The target processes' process names and mmap file paths are always real file paths. This is especially important once we do early inode uprobe registrations right before the task finder is started, where we also resolve the real inode for the PATH string without inspecting running processes (and also when we have to specify symlinks like /proc/PID/exe link for deleted ELF files).
Fixed in commit 81b2ee28207.