Activity for Michał Rogaliński
-
Michał Rogaliński committed [375d16]
- add tty_in terminal_in option for full control over separate terminal- make examine command show if command is builtin or not- spaces stuff- vscode configuration
-
- add tty_in terminal_in option for full control over separate terminal
-
further fixes, tested. Fix for failing tests in is set.sh...
-
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.
-
What is the issue here? Sorry, I totally misunderstood that. This is the integration test output, I get same error in "make check".
-
What is the issue here? I created 2 files: main.sh 1 2 3#!/bin/bash source test3.sh && echo success || echo fail test3.sh 1 2 3 4 5 6 7#!/bin/bash set -e (( 1 / 0)) echo eof As far as I can see, the debugger works as expected: prints fail when code as above prints eof\nsuccess when line is commented out: # (( 1 / 0))
-
Great, thank you for your help. I will reset my git fork...
-
Found additional small issue when showing bactrace and path has multiple spaces in bath: https://sourceforge.net/u/rogalmic/bashdb/ci/bdb0836764b24d783de564470b2604e52760fd37/ I think this fix is trivial and could also be taken.
-
Did the same for break.sh: https://sourceforge.net/u/rogalmic/bashdb/commit_browser
-
Please take a look at my new commit: https://sourceforge.net/u/rogalmic/bashdb/commit_browser This should be enough to explain this "almost accidental" feature :).
-
Seems to be working with double backslash + octal char code, i see no need to preceed with "-r" option in read.
-
After quick test maybe we do not need more changes - double "\\040" seems to do the trick (first for read, then for actual octal char code). I will verify this tomorrow.
-
After quick test maybe we do not need more changes - double "\040" seems to do the trick (first for read, then for actual octal char code). I will verify this tomorrow.
-
I am wondering how to do that. When i checked with original code, the "\" was beeing removed without the "-r" option in read. Do you propose to have a "if" only for break and load during read? It cannot be done lower in stack, because of the missing "\" after read. Perhaps there could be some mode in debugger that enables the raw operation ? Or is the "-r" breaking the core functionality?
-
Created initial changes, please take a look at newest commit: https://sourceforge.net/u/rogalmic/bashdb/commit_browser The change in load.sh is obvious. Processor.sh must not use read escaping, since then there is no control over using '\'. Requires testing if does not break anything. Filecache.sh was changed, because when i send first character '/' encoded as '\057', then check of first char ${ind_file:0:1} returns '\'. Could be a bad place for this operation... I have no idea how to create proper...
-
I would assume the issue comes from processor.sh line 149: if ! read _Dbg_cmd args <&$_Dbg_input_desc 2>&1; then The info about separate arguments is lost in single string + it seems that there is no simple fix for that, since the "Dbg_input_desc" would require some better interpretation then just separating via IFS. Maybe allownig octal character codes via escape character \ would serve as proper workaround? ("\000")
-
Source path with space - setting breakpoint fails
1
