On 3/1/2019 6:15 PM, Robert Elz wrote:
> Date:Fri, 1 Mar 2019 11:00:41 -0500
> From:Chet Ramey
> Message-ID: <91e964e9-a7e3-4f4e-ae9f-9ff3e3627...@case.edu>
>
> | It's wasteful and not particularly useful to have
> | the function definition text stored internall
Date:Fri, 1 Mar 2019 11:00:41 -0500
From:Chet Ramey
Message-ID: <91e964e9-a7e3-4f4e-ae9f-9ff3e3627...@case.edu>
| It's wasteful and not particularly useful to have
| the function definition text stored internally when you can regenerate an
| equivalent form from
On 2/27/19 4:19 PM, L A Walsh wrote:
>>> 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
On 2/26/2019 7:00 AM, Chet Ramey wrote:
> On 2/25/19 3:15 PM, L A Walsh wrote:
>
>
>> I don't 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
>> a
On 2/26/19 7:26 PM, L A Walsh wrote:
>>> 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
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
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."
> No
On 2/25/2019 6:53 AM, Chet Ramey wrote:
> Setting debugging mode in one of the startup files is an alternate way
> to start the bash debugger, equivalent to invoking bash with --debugger.
> It's been that way since the debugging support was introduced in bash-3.0.
>
I suspected that given the
On 2/24/19 9:39 PM, L A Walsh wrote:
> This is oddI wanted to turn on the file+line numbers on the function
> defs...thought it might help the debugger as it gets confused when
> functions are already in memory, but when I did that, now I get
> a weird error on login:
> /usr/share/bashdb/init/r
This is oddI wanted to turn on the file+line numbers on the function
defs...thought it might help the debugger as it gets confused when
functions are already in memory, but when I did that, now I get
a weird error on login:
/usr/share/bashdb/init/require.sh: line 17: _Dbg_requires: unbound vari
10 matches
Mail list logo
