Does bashdb work with bash 4.0?
If I run the tests before installing, I get:
Ran 10 tests. OK PASS: test-fns.sh test_print_frame test_frame_adjust ../../lib/frame.sh: line 34: return: -1: invalid option return: usage: return [n] ../../lib/frame.sh: line 34: return: -1: invalid option return: usage: return [n] ASSERT:expected:<0> but was:<2> ASSERT:expected:<0> but was:<2> ASSERT:expected:<0> but was:<2> Ran 2 tests. FAILED (failures=3)
Trying to debug any script, I get:
/usr/bin/../share/bashdb/lib/alias.sh: line 61: return: -1: invalid option return: usage: return [n]
Thanks.
The changes for bash 4.0 are in CVS but not part of a release yet.
Given the adoption of bash 4.0, possibly I'll make a new release around April 10th.
Log in to post a comment.
Does bashdb work with bash 4.0?
If I run the tests before installing, I get:
Ran 10 tests.
OK
PASS: test-fns.sh
test_print_frame
test_frame_adjust
../../lib/frame.sh: line 34: return: -1: invalid option
return: usage: return [n]
../../lib/frame.sh: line 34: return: -1: invalid option
return: usage: return [n]
ASSERT:expected:<0> but was:<2>
ASSERT:expected:<0> but was:<2>
ASSERT:expected:<0> but was:<2>
Ran 2 tests.
FAILED (failures=3)
Trying to debug any script, I get:
/usr/bin/../share/bashdb/lib/alias.sh: line 61: return: -1: invalid option
return: usage: return [n]
Thanks.
The changes for bash 4.0 are in CVS but not part of a release yet.
Given the adoption of bash 4.0, possibly I'll make a new release around April 10th.