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 5:42 PM, Olga Ustuzhanina wrote:
> On Mon, 25 Feb 2019 12:59:38 -0800
> L A Walsh wrote:
>
>> In this case, the decode of \xc2 doesn't swallow the following
>> character.
>
> I want to clarify that \xc2 (and other characters in the range
> mentioned above) can only swallow a \0. Other
On 2/25/19 10:47 PM, Chris King-Parra wrote:
> Bash Version: 4.4
> Patch Level:23
> Release Status: release
>
> Description:
> Executing the command "fc -0 -20" causes bash to crash
> and produce the error message '“bash” terminated by
>
> signal SIGSEGV (Address boundary erro
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
