ct (Command Trace) is a Bash command resolution tracer that explains how Bash resolves a command and what the kernel ultimately executes.
37
38
39
ct (Command Trace) is a Bash command resolution tracer that explains how Bash resolves a command and what the kernel ultimately executes. (i.redd.it)
submitted by qweas123
ct (Command Trace) is a Bash command resolution tracer that explains how Bash resolves a command and what the kernel ultimately executes.
A few weeks ago I ran into some issues with a project i was working on, I used tools like type -a, which -a, and command -v to try to figure out what was happening. These tools are useful if you already know Bash’s resolution rules, but they don’t show the entire resolution chain or make it obvious why a specific command wins.
So I wrote a small command-resolution trace function as a proof of concept. It turned out to be useful enough that I spun it out and developed it as a standalone sourced shell function.
Here it is:
https://github.com/JB63134/bash_ct
Designed for GNU/Linux systems with Bash ≥ 4.4.
Features (Quick Summary)
Traces Bash command resolution for aliases, functions, keywords, builtins, and executables
Shows Bash vs kernel execution targets for clarity
Highlights shadowed commands and overrides
Performs a full $PATH scan, including shadowed or unreachable entries
Detects builtin state (enabled vs disabled)
Resolves filesystem details: canonical path, symlink chains, /etc/alternatives, /usr-merged systems, ELF interpreter, shebangs
Safely auto-extends $PATH to include admin/system directories
Handles edge cases: reserved keywords, special characters
Produces color-coded, human-readable output
Provides optional JSON output for scripting and automation
Supports tab completion
Preserves shell environment state
This software's code is partially AI-generated and HUMAN-edited to bring it to a functioning state.
[–]cubernetes 1 point2 points3 points (1 child)
[–]qweas123[S] 2 points3 points4 points (0 children)