fix: Improve bash path detection and correct probe attachment #805
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit addresses two issues in the bash probe logic:
Unreliable Bash Path Discovery: The probe previously relied solely on the
$SHELL
environment variable. This could fail on systems where$SHELL
is not set to bash (e.g., using zsh or fish) or is not set at all.Incorrect Probe Attachment: When bash was dynamically linked with
libreadline.so
, the probe incorrectly used the path tolibreadline.so
for all function hooks. This failed for functions likeexecute_command
,exec_builtin
, andexit_builtin
which exist only in the main bash executable, not in the readline library.This patch introduces the following fixes:
/bin/bash
if a valid bash path cannot be determined from the$SHELL
variable.bash
executable and the path tolibreadline.so
.readline
target eitherlibreadline.so
(if present) or thebash
binary, while probes for other bash-internal functions always target thebash
binary itself.This change significantly improves the reliability and accuracy of bash command capturing across different system configurations.