search

Trepan-Debuggers / zshdb

gdb-like "trepan" debugger for zsh
GNU General Public License v3.0
295 stars 23 forks source link

failing tests #43

Open baodrate opened 1 year ago

baodrate commented 1 year ago

The tests test-frame and test-setshow are consistently failing on my system. I haven't investigated them yet, wanted to confirm if these were already known failures:

PASS: test-action
PASS: test-brkpt1
PASS: test-bug-args
PASS: test-bug-delete
PASS: test-bugIFS
PASS: test-bugIFS2
PASS: test-bug-errexit
PASS: test-bug-ksharrays
PASS: test-condition
PASS: test-debug
PASS: test-delete
PASS: test-enable
PASS: test-examine
PASS: test-export
FAIL: test-frame
PASS: test-list
PASS: test-multi
PASS: test-next
PASS: test-opts
PASS: test-restart
FAIL: test-setshow
PASS: test-skip
PASS: test-step
PASS: test-subshell
PASS: test-tbreak
rocky commented 1 year ago

These two tests are zsh version specific - the output you get depends on version of zsh. So what version are you using?

The simple way to see what's up is to cd into the test/integration and run the failing test. For example ./test-frame.

It will show a diff between the output you got versus the output expected.

baodrate commented 1 year ago

I see

zsh --version:

zsh 5.9 (x86_64-pc-linux-gnu)

test-frame:

@@ -79,7 +79,6 @@
 (hanoi.sh:42):
 +quit 
 zshdb: That's all, folks...
-ERROR AT: /tmp/zshdb/test/example/hanoi.sh:16 /tmp/zshdb/test/example/hanoi.sh:21 /tmp/zshdb/test/example/hanoi.sh:42 /tmp/zshdb/zshdb:141
 Debugged program terminated normally. Use q to quit or R to restart.
 +step 12
 ** The program is not being run.

^ odd because the error doesn't show up when I run zshdb interactively

test-setshow

--- /tmp/setshow-filtered.check 2023-04-04 19:11:48.377638534 -0500
+++ /tmp/zshdb/test/data/setshow-5.4.1.right    2023-04-03 14:47:40.750555360 -0500
@@ -345,7 +345,11 @@
 +quit
 zshdb: That's all, folks...
 Debugged program terminated normally. Use q to quit or R to restart.
+breakpoints
 No breakpoints have been set.
+
+stack
 ** The program is not being run.
+

 zshdb: That's all, folks...

not sure what's going on here either

rocky commented 1 year ago

Could it be that there are two different zsh versions installed: the one when you type zsh interactively and the one noted in the first line that starts #! in test-frame?