On 10/12/15 4:16 PM, Nicholas Bamber wrote: > My investigations indicate that it is still true that as per Debian bug > report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403304) > --debugger does NOT start the debugger UNLESS the debugged script has a $1.
We discussed this in a thread on bug-bash back in April: http://lists.gnu.org/archive/html/bug-bash/2015-04/msg00183.html This discussion references an earlier bug report concerning whether the --debugger option should produce an error if the bashdb script is not installed. There is also an issue with bashdb misbehaving when run in an interactive shell; that was the reason for the check of $1 in the first place. Part of that thread explains why a check of $0 is not correct: since $0 is always set, a check for it has no effect. The final change that solves both problems went into the bash development branch in early May, and will be in bash-4.4. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
