Re: turning on file+line for functions with shopt -s extdebug gives error

[L A Walsh]

On 2/26/2019 7:00 AM, Chet Ramey wrote:
> On 2/25/19 3:15 PM, L A Walsh wrote:
>
>   
>> In looking at the bash manpage, I find that 'extdebug' documents
>> the turning on and saving of source and line numbers, but I don't
>> see where it documents running the bash debugger.
>>     
>
> I'll add something in addition to the "If set at shell invocation."
>
>   
>> Nor do I see where function-tracing and error tracing are defined.
>>     
>
> set -o functrace/set -T
> set -o errtrace/set -E
>   
--
>   
>> Are they defined "somewhere"?  Maybe a short note as to what they
>> are might be added to the manpage where the terms are used (under
>> description of shopt+extdebug)?
>>     
>
> They're described in the FUNCTIONS section, since they affect function
> behavior.
>   
----
    Ahh...maybe a cross-reference would help? I.e. see FUNCTIONS for more
info?
> The debugger is very impressive. It's a separate project, so you should
> probably contact the author with your suggestions.
>   
Yes, think I mentioned that at the beginning of this chain.

The part about turning on filenames+line numbers for function definitions
is in bash.  If those aren't on, the debugger can't find them.

Also, the desire to retain the original source format of code is another
"in bash" issue.  Perhaps it could be tied or related to the turning on
of function definition locations.

Both of those are issues "in bash" before a bash debugger has ever
been invoked.