Thread: [Bashdb-help] bashdb 4.3-0.9: `shopt -s nullglob` results in hung process

If the script to be debugged has set `shopt -s  nullglob` before 
`bashdb-trace` is sourced, then bashdb either hangs at the line it is 
invoked with `_Dbg_debugger` or at the debugger quit/restart prompt if 
not. Perhaps the script's shell options could be saved and restored 
with:

old_shopt=$(shopt -p)

and:

eval "$old_shopt" 2> /dev/null

so that the debugger isn't affected by what the script's shell options 
are.

Cheers
John

Should be fixed in commit a9e7dcb. shopt nullglob saved and restored as
suggested.

On Mon, Nov 3, 2014 at 3:26 AM, John Purnell <joh...@gm...> wrote:

> If the script to be debugged has set `shopt -s  nullglob` before
> `bashdb-trace` is sourced, then bashdb either hangs at the line it is
> invoked with `_Dbg_debugger` or at the debugger quit/restart prompt if
> not. Perhaps the script's shell options could be saved and restored
> with:
>
> old_shopt=$(shopt -p)
>
> and:
>
> eval "$old_shopt" 2> /dev/null
>
> so that the debugger isn't affected by what the script's shell options
> are.
>
> Cheers
> John
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bashdb-help mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>