Collect selected cli args and pass them to sub-invocations of bashrc

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.

[hawicz]

…through the "debug" command. Fixes Issue #71

[rocky]

@hawicz Thanks for doing this. I'll look at this in detail a little later.

[rocky]

I needed to add:

_Dbg_libdir:-L=

because, my initial bash invocation was:

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

Here is what I got initially without the above change (following the issue instructions):

$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
/tmp/bashdb/init/opts.sh: line 294: ((: /tmp/bashdb: syntax error: operand expected (error token is "/tmp/bashdb")
(/tmp/somescript:1):
1:	/tmp/otherscript
bashdb<0> bashdb: That's all, folks...

[rocky]

It all looks good, but I think there is one more bashdb variable that needs to get passed through (Ddbg_dir or the -L option).

The thing I'd ask though, is to work up some test for this. It could either be a unit test using shunit (in test/unit) or an integration tests (in test/integration) or both — up to you.

[hawicz]

Hmm... I thought there already was special handling for the -L option, and I didn't want to duplicate what that was doing. I'll take a other look

[hawicz]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0

Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

[rocky]

cd /tmp
git clone git clone https://github.com/hawicz/bashdb
cd bashdb
./autogen.sh
./configure --prefix /tmp/inst
make && make install

Followed by the steps from #71, except I changed the bashdb command to:

/tmp/inst/bin/bashdb -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

uerh@LAPTOP-UVU6TEG3:/tmp/bashdb/myrepo$ git checkout HEAD
bash debugger, bashdb, release 5.2-1.2.0
Copyright 2002-2004, 2006-2012, 2014, 2016-2019, 2021, 2023-2024 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
(/tmp/somescript:1):
1: /tmp/otherscript
bashdb<0> debug
Debugging new script with /usr/bin/bash /tmp/inst/bin/bashdb -q -L /tmp/inst/share/bashdb --tty /dev/tty --tty_in /dev/tty --tempdir /tmp -- /tmp/otherscript
(/tmp/otherscript:1):
1: echo in otherscript

I also tried using the uninstalled script from /tmp/bashdb with

/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript

but with the same working result. I'm using bash 5.2.37.

the relevant lines in opts.sh are:

 293 elif (( subarg_var )) ; then
294 _Dbg_subdebug_args+=("${subarg_cli%}")
295 fi

So I don't understand how you could have seen that error on line 294.

One can get this behavior if you have bashdb installed in the place that bash thinks bashdb should be installed by default. (This might be "/usr/share/bashdb/bashdb-main.inc")

Make sure you do not have bashdb installed before running this test.

[hawicz]

Here's a full set of steps to use a completely clean environment:

• First, create a testscript.sh file:

cat <<"TTTT" > testscript.sh
set -e -x -v
trap 'echo Failed!' EXIT
if which apt-get > /dev/null ; then
apt-get update
apt-get install -y autoconf binutils make texinfo git
else
apk update
apk add autoconf automake binutils make texinfo git bash
fi
cd /tmp
git clone "${URL}" bashdb
cd bashdb
sh autogen.sh
make
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
# Create a minimal git repo
git init myrepo
cd myrepo
touch foo ; git add foo ; git commit -m foo foo
# Set up the hook scripts:
cat <<EOF > .git/hooks/post-checkout
/tmp/bashdb/bashdb -L /tmp/bashdb --tty /dev/tty --tty_in /dev/tty /tmp/somescript
EOF
chmod +x .git/hooks/post-checkout
echo "/tmp/otherscript" > /tmp/somescript
echo "echo end of somescript" >> /tmp/somescript
echo "echo in otherscript" > /tmp/otherscript
echo "echo another line" >> /tmp/otherscript
chmod +x /tmp/*script
git checkout HEAD # Trigger the hook
trap '' EXIT
TTTT
chmod +x testscript.sh

• Then start a docker container with the relevant repo to test:

TEST1=https://github.com/Trepan-Debuggers/bashdb/
TEST2=https://github.com/hawicz/bashdb/
docker run -it --rm -e URL=$TEST2 --mount type=bind,src=$(pwd)/testscript.sh,dst=/tmp/testscript.sh debian:trixie

• Then once in docker, run the test script and you should end up in bashdb:

/tmp/testscript.sh

I also tried with ubuntu:noble, and ubuntu:questing (ubuntu:latest doesn't work b/c it has bash 5.3), and alpine:3.22, and in each case it worked fine.

[rocky]

Here's a full set of steps to use a completely clean environment:
...

I just had a chance to try this. Although I had problems with the scripts, after adjusting things, everything worked.

Although there is still the issue that I got what I got (we haven't proved there is no bug), I guess we'll go with this, and if problems arise down the line, we'll deal with that then.