Re: bash --debugger does nothing if debug script not installed

[Ryan Cunningham]

On Nov 23, 2014, at 10:58 AM, Chet Ramey <chet.ramey@case.edu> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
>> On 11/21/14 9:31 PM, Eric Blake wrote:
>> 
>> $ bash --debugger foo
>> bash: debug script /usr/bin/bashdb: file not found
>> 
>> to give me a heads up that I need to install bashdb.  Would it make
>> sense to make the explicit use of --debugger be fatal if a debugger
>> start file is configured but not present?
> 
> I think a better change is to report the error on opening the file,
> then turn off debugging mode but allow script execution to continue.
> Something like this:
> 
> $ bash --debugger foo
> foo: /usr/local/share/bashdb/bashdb-main.inc: No such file or directory
> foo: warning: cannot start debugger; debugging mode disabled
> hello

Maybe something like this:

bash: foo: debugger /usr/local/share/bashdb/bashdb-main.inc: No such file or 
directory
bash: foo: disabling debugging mode
hello

Messages above that begin with "bash:" should be directed to file descriptor 2.

> 
> Chet
> - -- 
> ``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/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> 
> iEYEARECAAYFAlRyLmsACgkQu1hp8GTqdKsgOwCfb3SiB1jq4R9LzjI50NbsonAC
> LL4An2u9/xUTvrDJjsYrJxqp2u0VUTVE
> =EziL
> -----END PGP SIGNATURE-----
>