bash debugger / Bugs / #52 FAIL: test-bug-set-e

Dave Cooper - 2018-08-14

Any thoughts on this? I have a very large project to do, and would like to be able to debug. Thoughts are apprecaited.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michał Rogaliński - 2018-08-27

What is the issue here?

Sorry, I totally misunderstood that. This is the integration test output, I get same error in "make check".

Last edit: Michał Rogaliński 2018-08-27

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michał Rogaliński - 2018-08-27

bashdb: cannot read program to debug: /Users/dcooper/Downloads/bashdb-4.4-0.94/test/example/bug-set-e.sh.

Looks like file is missing from #94 build package:
test/example/bug-set-e.sh

After taking the file from master branch, test passes. "make check" is not needed to install bashdb.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Whissi - 2018-11-14

There's more than just one file missing in bashdb-4.4.1.0.0 release tarball:

missing-files/ ├── data │ ├── file with spaces.cmd │ ├── file with spaces.right │ ├── sig-44.cmd │ └── sig-bug.cmd └── example ├── bug-set-e.sh ├── dir with spaces │ └── bug.sh ├── file with spaces.sh └── sig-bug.sh

Not sure if the sig-* files are required but with these files added we get full test coverage in Gentoo:

PASS: test-bug-step-subshell PASS: test-complete PASS: test-file-with-spaces PASS: test-export PASS: test-info-args SKIP: test-sig PASS: test-debug PASS: test-delete PASS: test-setshow PASS: test-action PASS: test-bug-args PASS: test-bugI PASS: test-misc PASS: test-bugIFS PASS: test-bug-set-e PASS: test-bug-loc PASS: test-bug-source PASS: test-command PASS: test-display PASS: test-interrupt PASS: test-enable PASS: test-list PASS: test-finish PASS: test-frame PASS: test-brkpt PASS: test-search PASS: test-lopts PASS: test-restart PASS: test-parm PASS: test-settrace PASS: test-skip PASS: test-bug-clear PASS: test-bug-step PASS: test-bug-break PASS: test-sopts PASS: test-watch1 PASS: test-watch2 PASS: test-multi PASS: test-subshell PASS: test-tbreak PASS: test-trace ============================================================================ Testsuite summary for bashdb 4.4-1.0.0 ============================================================================ # TOTAL: 43 # PASS: 42 # SKIP: 1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Rocky Bernstein - 2018-11-14
  
  I have changed the various Makefile.am's to include into the tarball:
  
  test/data/Makefile.am
  + sig-44.cmd \ + sig-bug.cmd \
  
  test/example/Makefile.am
  + bug-set-e.sh \ + sig-bug.sh \
  
  test/integration/Makefile.am
  + test-bug-set-e \
  
  However right now I can't push to sourceforge. I've opened an issue
  regarding this:
  
  https://sourceforge.net/p/forge/site-support/18731/
  
  On Wed, Nov 14, 2018 at 5:00 PM Whissi whissi@users.sourceforge.net wrote:
  
  There's more than just one file missing in bashdb-4.4.1.0.0 release
  tarball:
  
  missing-files/
  ├── data
  │ ├── file with spaces.cmd
  │ ├── file with spaces.right
  │ ├── sig-44.cmd
  │ └── sig-bug.cmd
  └── example
  ├── bug-set-e.sh
  ├── dir with spaces
  │ └── bug.sh
  ├── file with spaces.sh
  └── sig-bug.sh
  
  Not sure if the sig-* files are required but with these files added we get
  full test coverage in Gentoo:
  
  PASS: test-bug-step-subshellPASS: test-completePASS: test-file-with-spacesPASS: test-exportPASS: test-info-argsSKIP: test-sigPASS: test-debugPASS: test-deletePASS: test-setshowPASS: test-actionPASS: test-bug-argsPASS: test-bugIPASS: test-miscPASS: test-bugIFSPASS: test-bug-set-ePASS: test-bug-locPASS: test-bug-sourcePASS: test-commandPASS: test-displayPASS: test-interruptPASS: test-enablePASS: test-listPASS: test-finishPASS: test-framePASS: test-brkptPASS: test-searchPASS: test-loptsPASS: test-restartPASS: test-parmPASS: test-settracePASS: test-skipPASS: test-bug-clearPASS: test-bug-stepPASS: test-bug-breakPASS: test-soptsPASS: test-watch1PASS: test-watch2PASS: test-multiPASS: test-subshellPASS: test-tbreakPASS: test-trace============================================================================Testsuite summary for bashdb 4.4-1.0.0============================================================================# TOTAL: 43# PASS: 42# SKIP: 1
  
  [bugs:#52] https://sourceforge.net/p/bashdb/bugs/52/ FAIL:
  test-bug-set-e*
  
  Status: open
  Group: v1.0_(example)
  Created: Fri Aug 10, 2018 03:48 PM UTC by Dave Cooper
  Last Updated: Mon Aug 27, 2018 12:40 PM UTC
  Owner: nobody
  
  OS: Mac OS X 10.13.6
  Bash version: GNU bash, version 4.4.23(1)-release
  (x86_64-apple-darwin17.5.0)
  bashdb 4.4-0.94
  FAIL: test-bug-set-e
  
  bashdb: cannot read program to debug:
  /Users/dcooper/Downloads/bashdb-4.4-0.94/test/example/bug-set-e.sh.
  
  /Users/dcooper/Downloads/bashdb-4.4-0.94/test/integration/bug-set-e.check
  2018-08-10 10:40:36.000000000 -0500
  +++ /Users/dcooper/Downloads/bashdb-4.4-0.94/test/data/bug-set-e.right
  2017-07-31 23:43:16.000000000 -0500
  @@ -1 +1,18 @@
  -INVESTIGATE EXIT FAILURE: [1 => exit (1)]
  +(bug-set-e.sh:2):
  +2: x=1
  ++# Debugger test to see that set -e is respected and we can step through
  it
  ++step
  +(bug-set-e.sh:4):
  +4: set -e
  ++step
  +(bug-set-e.sh:6):
  +6: echo hi
  ++step
  +hi
  +(bug-set-e.sh:7):
  +7: (( 1 / 0))
  ++step
  +(bug-set-e.sh:1):
  +1: #!/bin/bash
  ++quit
  +bashdb: That's all, folks...
  FAIL test-bug-set-e (exit status: 1)
  
  Sent from sourceforge.net because you indicated interest in
  https://sourceforge.net/p/bashdb/bugs/52/
  
  To unsubscribe from further messages, please visit
  https://sourceforge.net/auth/subscriptions/
  
  Related
  
  Bugs: ~~#52~~
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Rocky Bernstein - 2018-11-14
    
    Also, Make can't deal with filenames with spaces in them. I have tried
    escaping the blank and although that is alleged to work
    https://www.cmcrossroads.com/article/gnu-make-meets-file-names-spaces-them
    it didn't when I put this inside a Makefile variable.
    
    There is probably some way to work around Makefile.am or post hook thing to
    append to the tarball, but I'll leave that for someone else to figure out
    how to do.
    
    On Wed, Nov 14, 2018 at 6:01 PM Rocky Bernstein rocky.bernstein@gmail.com
    wrote:
    
    I have changed the various Makefile.am's to include into the tarball:
    
    test/data/Makefile.am
    + sig-44.cmd \ + sig-bug.cmd \
    
    test/example/Makefile.am
    + bug-set-e.sh \ + sig-bug.sh \
    
    test/integration/Makefile.am
    + test-bug-set-e \
    
    However right now I can't push to sourceforge. I've opened an issue
    regarding this:
    
    https://sourceforge.net/p/forge/site-support/18731/
    
    On Wed, Nov 14, 2018 at 5:00 PM Whissi whissi@users.sourceforge.net
    wrote:
    
    There's more than just one file missing in bashdb-4.4.1.0.0 release
    tarball:
    
    missing-files/
    ├── data
    │ ├── file with spaces.cmd
    │ ├── file with spaces.right
    │ ├── sig-44.cmd
    │ └── sig-bug.cmd
    └── example
    ├── bug-set-e.sh
    ├── dir with spaces
    │ └── bug.sh
    ├── file with spaces.sh
    └── sig-bug.sh
    
    Not sure if the sig-* files are required but with these files added we
    get full test coverage in Gentoo:
    
    PASS: test-bug-step-subshellPASS: test-completePASS: test-file-with-spacesPASS: test-exportPASS: test-info-argsSKIP: test-sigPASS: test-debugPASS: test-deletePASS: test-setshowPASS: test-actionPASS: test-bug-argsPASS: test-bugIPASS: test-miscPASS: test-bugIFSPASS: test-bug-set-ePASS: test-bug-locPASS: test-bug-sourcePASS: test-commandPASS: test-displayPASS: test-interruptPASS: test-enablePASS: test-listPASS: test-finishPASS: test-framePASS: test-brkptPASS: test-searchPASS: test-loptsPASS: test-restartPASS: test-parmPASS: test-settracePASS: test-skipPASS: test-bug-clearPASS: test-bug-stepPASS: test-bug-breakPASS: test-soptsPASS: test-watch1PASS: test-watch2PASS: test-multiPASS: test-subshellPASS: test-tbreakPASS: test-trace============================================================================Testsuite summary for bashdb 4.4-1.0.0============================================================================# TOTAL: 43# PASS: 42# SKIP: 1
    
    [bugs:#52] https://sourceforge.net/p/bashdb/bugs/52/ FAIL:
    test-bug-set-e*
    
    Status: open
    Group: v1.0_(example)
    Created: Fri Aug 10, 2018 03:48 PM UTC by Dave Cooper
    Last Updated: Mon Aug 27, 2018 12:40 PM UTC
    Owner: nobody
    
    OS: Mac OS X 10.13.6
    Bash version: GNU bash, version 4.4.23(1)-release
    (x86_64-apple-darwin17.5.0)
    bashdb 4.4-0.94
    FAIL: test-bug-set-e
    
    bashdb: cannot read program to debug:
    /Users/dcooper/Downloads/bashdb-4.4-0.94/test/example/bug-set-e.sh.
    
    /Users/dcooper/Downloads/bashdb-4.4-0.94/test/integration/bug-set-e.check
    2018-08-10 10:40:36.000000000 -0500
    +++ /Users/dcooper/Downloads/bashdb-4.4-0.94/test/data/bug-set-e.right
    2017-07-31 23:43:16.000000000 -0500
    @@ -1 +1,18 @@
    -INVESTIGATE EXIT FAILURE: [1 => exit (1)]
    +(bug-set-e.sh:2):
    +2: x=1
    ++# Debugger test to see that set -e is respected and we can step through
    it
    ++step
    +(bug-set-e.sh:4):
    +4: set -e
    ++step
    +(bug-set-e.sh:6):
    +6: echo hi
    ++step
    +hi
    +(bug-set-e.sh:7):
    +7: (( 1 / 0))
    ++step
    +(bug-set-e.sh:1):
    +1: #!/bin/bash
    ++quit
    +bashdb: That's all, folks...
    FAIL test-bug-set-e (exit status: 1)
    
    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/bashdb/bugs/52/
    
    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/
    
    Related
    
    Bugs: ~~#52~~
    
    alternate
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Rocky Bernstein - 2018-11-15

Was able to push to sourceforge this morning. Attached is a tarball made from the recent changes. If that is suitable, I will push it as a release.

bashdb-4.4-0.95.tar.bz2

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Whissi - 2018-11-15
  
  Looks good aside test-file-with-spaces:
  
  make check-TESTS [207/95825] make[3]: Entering directory '/var/tmp/portage/app-shells/bashdb-4.4.1.0.0/work/bashdb-4.4-0.95/test/integration' make[4]: Entering directory '/var/tmp/portage/app-shells/bashdb-4.4.1.0.0/work/bashdb-4.4-0.95/test/integration' PASS: test-bug-set-e SKIP: test-file-with-spaces PASS: test-bug-step-subshell PASS: test-complete PASS: test-export PASS: test-info-args SKIP: test-sig PASS: test-delete PASS: test-debug PASS: test-setshow PASS: test-action PASS: test-bug-args PASS: test-bugI PASS: test-misc PASS: test-bugIFS PASS: test-bug-loc PASS: test-command PASS: test-bug-source PASS: test-display PASS: test-enable PASS: test-finish PASS: test-frame PASS: test-list PASS: test-interrupt PASS: test-search PASS: test-brkpt PASS: test-restart PASS: test-parm PASS: test-lopts PASS: test-skip PASS: test-settrace PASS: test-settrace PASS: test-bug-clear PASS: test-bug-step PASS: test-sopts PASS: test-bug-break PASS: test-watch2 PASS: test-subshell PASS: test-watch1 PASS: test-multi PASS: test-tbreak PASS: test-trace ============================================================================ Testsuite summary for bashdb 4.4-0.95 ============================================================================ # TOTAL: 44 # PASS: 41 # SKIP: 3 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 ============================================================================
  
  But just to be sure: I hope whatever you are going to release will be > 4.4-1.0.0 ...
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Rocky Bernstein - 2018-11-15
    
    I hope whatever you are going to release will be > 4.4-1.0.0 ...
    
    Sure, we'll go with our first 1.0.0 release. Probably will do over the
    upcoming weekend.
    
    On Thu, Nov 15, 2018 at 9:55 AM Whissi whissi@users.sourceforge.net wrote:
    
    Looks good aside test-file-with-spaces:
    
    make check-TESTS [207/95825]
    make[3]: Entering directory '/var/tmp/portage/app-shells/bashdb-4.4.1.0.0/work/bashdb-4.4-0.95/test/integration'
    make[4]: Entering directory '/var/tmp/portage/app-shells/bashdb-4.4.1.0.0/work/bashdb-4.4-0.95/test/integration'
    PASS: test-bug-set-e
    SKIP: test-file-with-spaces
    PASS: test-bug-step-subshell
    PASS: test-complete
    PASS: test-export
    PASS: test-info-args
    SKIP: test-sig
    PASS: test-delete
    PASS: test-debug
    PASS: test-setshow
    PASS: test-action
    PASS: test-bug-args
    PASS: test-bugI
    PASS: test-misc
    PASS: test-bugIFS
    PASS: test-bug-loc
    PASS: test-command
    PASS: test-bug-source
    PASS: test-display
    PASS: test-enable
    PASS: test-finish
    PASS: test-frame PASS: test-list
    PASS: test-interrupt PASS: test-search
    PASS: test-brkpt
    PASS: test-restart
    PASS: test-parm PASS: test-lopts
    PASS: test-skip PASS: test-settrace
    PASS: test-settrace
    PASS: test-bug-clear
    PASS: test-bug-step
    PASS: test-sopts
    PASS: test-bug-break
    PASS: test-watch2
    PASS: test-subshell
    PASS: test-watch1
    PASS: test-multi
    PASS: test-tbreak
    PASS: test-trace
    ============================================================================
    Testsuite summary for bashdb 4.4-0.95
    ============================================================================
    
    TOTAL: 44
    
    PASS: 41
    
    SKIP: 3
    
    XFAIL: 0
    
    FAIL: 0
    
    XPASS: 0
    
    ERROR: 0
    
    ============================================================================
    
    But just to be sure: I hope whatever you are going to release will be >
    4.4-1.0.0 ...
    
    [bugs:#52] https://sourceforge.net/p/bashdb/bugs/52/ FAIL:
    test-bug-set-e*
    
    Status: open
    Group: v1.0_(example)
    Created: Fri Aug 10, 2018 03:48 PM UTC by Dave Cooper
    Last Updated: Thu Nov 15, 2018 02:45 PM UTC
    Owner: nobody
    
    OS: Mac OS X 10.13.6
    Bash version: GNU bash, version 4.4.23(1)-release
    (x86_64-apple-darwin17.5.0)
    bashdb 4.4-0.94
    FAIL: test-bug-set-e
    
    bashdb: cannot read program to debug:
    /Users/dcooper/Downloads/bashdb-4.4-0.94/test/example/bug-set-e.sh.
    
    /Users/dcooper/Downloads/bashdb-4.4-0.94/test/integration/bug-set-e.check
    2018-08-10 10:40:36.000000000 -0500
    +++ /Users/dcooper/Downloads/bashdb-4.4-0.94/test/data/bug-set-e.right
    2017-07-31 23:43:16.000000000 -0500
    @@ -1 +1,18 @@
    -INVESTIGATE EXIT FAILURE: [1 => exit (1)]
    +(bug-set-e.sh:2):
    +2: x=1
    ++# Debugger test to see that set -e is respected and we can step through
    it
    ++step
    +(bug-set-e.sh:4):
    +4: set -e
    ++step
    +(bug-set-e.sh:6):
    +6: echo hi
    ++step
    +hi
    +(bug-set-e.sh:7):
    +7: (( 1 / 0))
    ++step
    +(bug-set-e.sh:1):
    +1: #!/bin/bash
    ++quit
    +bashdb: That's all, folks...
    FAIL test-bug-set-e (exit status: 1)
    
    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/bashdb/bugs/52/
    
    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/
    
    Related
    
    Bugs: ~~#52~~
    
    alternate
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Whissi - 2018-11-15
      
      Sure, we'll go with our first 1.0.0 release. Probably will do over the upcoming weekend.
      
      Just to be sure that I understand and we are talking abou the same. It looks like you created a not yet published "4.4-0.95" tag for the test attachment but there is already a published release-4.4-1.0.0 tag (https://sourceforge.net/p/bashdb/code/ref/master/tags/). So when you are going to release something new over the upcoming weekend please make sure to release "4.4-1.0.1" for example. :)
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Rocky Bernstein - 2018-11-15
        
        Ok. 1.0.1 then.
        
        On Thu, Nov 15, 2018 at 11:13 AM Whissi whissi@users.sourceforge.net
        wrote:
        
        Sure, we'll go with our first 1.0.0 release. Probably will do over the
        upcoming weekend.
        
        Just to be sure that I understand and we are talking abou the same. It
        looks like you created a not yet published "4.4-0.95" tag for the test
        attachment but there is already a published release-4.4-1.0.0 tag (
        https://sourceforge.net/p/bashdb/code/ref/master/tags/). So when you are
        going to release something new over the upcoming weekend please make sure
        to release "4.4-1.0.1" for example. :)
        
        [bugs:#52] https://sourceforge.net/p/bashdb/bugs/52/ FAIL:
        test-bug-set-e*
        
        Status: open
        Group: v1.0_(example)
        Created: Fri Aug 10, 2018 03:48 PM UTC by Dave Cooper
        Last Updated: Thu Nov 15, 2018 02:55 PM UTC
        Owner: nobody
        
        OS: Mac OS X 10.13.6
        Bash version: GNU bash, version 4.4.23(1)-release
        (x86_64-apple-darwin17.5.0)
        bashdb 4.4-0.94
        FAIL: test-bug-set-e
        
        bashdb: cannot read program to debug:
        /Users/dcooper/Downloads/bashdb-4.4-0.94/test/example/bug-set-e.sh.
        
        /Users/dcooper/Downloads/bashdb-4.4-0.94/test/integration/bug-set-e.check
        2018-08-10 10:40:36.000000000 -0500
        +++ /Users/dcooper/Downloads/bashdb-4.4-0.94/test/data/bug-set-e.right
        2017-07-31 23:43:16.000000000 -0500
        @@ -1 +1,18 @@
        -INVESTIGATE EXIT FAILURE: [1 => exit (1)]
        +(bug-set-e.sh:2):
        +2: x=1
        ++# Debugger test to see that set -e is respected and we can step through
        it
        ++step
        +(bug-set-e.sh:4):
        +4: set -e
        ++step
        +(bug-set-e.sh:6):
        +6: echo hi
        ++step
        +hi
        +(bug-set-e.sh:7):
        +7: (( 1 / 0))
        ++step
        +(bug-set-e.sh:1):
        +1: #!/bin/bash
        ++quit
        +bashdb: That's all, folks...
        FAIL test-bug-set-e (exit status: 1)
        
        Sent from sourceforge.net because you indicated interest in
        https://sourceforge.net/p/bashdb/bugs/52/
        
        To unsubscribe from further messages, please visit
        https://sourceforge.net/auth/subscriptions/
        
        Related
        
        Bugs: ~~#52~~
        
        alternate
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Rocky Bernstein - 2018-11-17

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

FAIL: test-bug-set-e

bash debugger

Group

Searches

Help

#52 FAIL: test-bug-set-e

FAIL: test-bug-set-e

Related

Discussion

Related

Related

TOTAL: 44

PASS: 41

SKIP: 3

XFAIL: 0

FAIL: 0

XPASS: 0

ERROR: 0

Related

Related