[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bash 4.4 and BASHOPTS containing extdebug in env
From: |
Chet Ramey |
Subject: |
Re: bash 4.4 and BASHOPTS containing extdebug in env |
Date: |
Wed, 27 Apr 2016 09:17:57 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0 |
On 4/26/16 10:49 PM, Grisha Levit wrote:
> Thanks for the explanation. I'd read that thread but thought the change
> was supposed to only modify the behavior when explicitly specifying the
> --debugger option. That also seems to be the gist of the original RedHat
> bugzilla request that prompted the
> thread: https://bugzilla.redhat.com/show_bug.cgi?id=1165793
That's the thing. They set the same option and enable the same behavior,
and have always been tied together like that. It's kind of like --posix
and -o posix.
If that option is enabled when the shell starts up, the shell attempts to
load the debugger start file, which creates the debugging environment.
> Maybe the description of the extdebug option to the shopt builtin can be
> modified with something like
I'll add something.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/