#69 5.0-1.1.2 test fail

[krbvroc1]

5.0-1.1.2 - 1 failure from 'make check'

GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
(Ubuntu 20.04.2 LTS)

## FAIL: test-bug-loc
## ==================

--- bashdb-5.0-1.1.2/test/integration/bug-loc.check 2021-02-01 11:00:00.246099517 -0500
+++ bashdb-5.0-1.1.2/test/data/bug-loc.right    2019-10-10 08:12:31.000000000 -0400
@@ -1,13 +1,13 @@
 (bug-loc.sh:5):
-5: dirname=${BASH_SOURCE%/*}   # equivalent to dirname($0)
+5: dirname=${BASH_SOURCE%/*}   # equivalent to dirname($0)
 +# Test to see that we read in files that mentioned in breakpoints
 +# but we don't step into.
 +step 
 (bug-loc.sh:6):
-6: source ${dirname}/library.sh
+6: source ${dirname}/library.sh
 +step 
 (bug-loc.sh:7):
-7: echo 'script line 7'
+7: echo 'script line 7'
 +step 
 script line 7
 (bug-loc.sh:8):
@@ -17,10 +17,10 @@
 1: library-function() {
 +step 
 (library.sh:2):
-2:   echo 'library line 2 in library-function'
+2:   echo 'library line 2 in library-function'
 +step 
 library line 2 in library-function
 (bug-loc.sh:11):
-11:    echo 'script line 11'
+11:    echo 'script line 11'
 +quit 
 bashdb: That's all, folks...
FAIL test-bug-loc (exit status: 1)

[Rocky Bernstein]

The above are diffs in between expected output and actual output. I don't see a difference, above even looking at this in decoding the individual characters and looking for differences in spaces and the use of tabs or not.

Possibly in cut and paste the characters were converted to the same thing if say cut and paste were used.

I'll guess you have a locale set that might be using some subtle different character codes for quote.

At any rate, with the above information there's nothing to go on yet.

[krbvroc1]

The difference appears to be some sort of bash colorization escape codes in your 'bug-loc.right' file. I have bash colors disabled on my system.