Re: Bash debugging.

[Chet Ramey]

On 10/5/24 4:14 PM, David Shuman wrote:
> I have been working on several items as I am using bash to configure
> systems.
>
> I started wanting to log the output of my scripts.  Then I added a prefixed
> message construct so detailed logs could be summarized without extraneous
> debugging information (I have written an extract program using c in the
> past that could also probably be written in bash (readlng a line at a time
> from the log file}. The code is expected to be modified to establish
> project oriented bash environment settings for the execution of the
> configuration scripts.   I have a function to print the bash reverse
> function trace and the accumulated arguments table (BASH_ARGV).  The
> function is user callable .It can also be issued as the first statement of
> a function call (a function trace option).  Most importantly the reverse
> trace is in theory (currently being tested as the initial processing for
> trap statements.
>
> Does this sound potentially like a section of the bash handbook?

It sounds like it could be a standalone document describing this
particular approach. I'd be glad to look at it.

Chet

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

OpenPGP_signature.asc
Description: OpenPGP digital signature