[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: turning on file+line for functions with shopt -s extdebug gives erro
L A Walsh
Re: turning on file+line for functions with shopt -s extdebug gives error
Sun, 03 Mar 2019 07:00:57 -0800
On 3/1/2019 6:15 PM, Robert Elz wrote:
> Date: Fri, 1 Mar 2019 11:00:41 -0500
> From: Chet Ramey <address@hidden>
> Message-ID: <address@hidden>
> | It's wasteful and not particularly useful to have
> | the function definition text stored internally when you can regenerate an
> | equivalent form from the compiled function definition.
> I actually much prefer to see the shell regenerated form - if I want the
> original I have the sources, but seeing the shell "reverse compiled" form
> gives a different perspective to the code, and sometimes allows bugs to be
> made obvious which get hidden by the formatting of the original.
To be clear, I've never suggested getting rid of the reformatted
but if you are looking for the source of a bug, and single stepping through
the program, it does help if what you see matches what is in the file.
Also, the source file may not no longer correspond to the reformatted
version it may have:
- been moved, unmounted or mounted over,
- been edited, (or)
- be inaccessible due to a change in access.
You think you have sources, but how many times have you entered
a script before it was written to disk, for example?
Please store source file name + line number for all functions defined whether or not bashdb is running., L A Walsh, 2019/03/01