Open GoogleCodeExporter opened 8 years ago
That would require some thinking. Perhaps it's possible to use some generated
pattern instead of BASH_SOURCE, but I'm not sure.
As you might have noticed, I'm not very active in updating shcov anymore (to
say the least). There are some other people that has improved the code a bit at
github, so I guess I should start merging back that code soon.
Original comment by simon.ka...@gmail.com
on 8 Feb 2014 at 2:30
Good news! Since bash 4.3 this problems is no more as bash changed the
indirection_string from a static buffer to a dynamic buffer.
from the changelog.
print_cmd.c
- change indirection_string from a static buffer to a dynamic one
managed by indirection_level_string(), so we don't end up truncating
PS4. Suggested by Dennis Williamson <addresswithheld>
Original comment by mab...@gmail.com
on 9 Feb 2015 at 3:33
Good to hear!
Also good news: I've deprecated shcov in favor of kcov
(https://github.com/SimonKagstrom/kcov), which has many more features and fixes
at least a few of the bugs shcov had.
Although I tought it would have had this particular problem as well, but
apparently that fixed itself! :-)
Original comment by simon.ka...@gmail.com
on 9 Feb 2015 at 3:36
That's great news. Unfortunately, our system admins aren't amenable to
installing bash/4.3 on all of the RHEL6 machines they support, and there are
many. (If 4.3 is the default with the next version of RHEL we'll get it, but
not until then.) I've been testing out kcov recently, and it seems to encounter
this issue also (with Bash-4.1.2) though the reproduction commands I provided
with this issue don't seem to cause it. I'll have to investigate some more
before I submit an issue on the kcov site.
Original comment by mham...@sandia.gov
on 25 Feb 2015 at 8:49
I don't know how your test suite looks like, but would it be possible to
locally build a bash for use in the test suites? In that case, you could use
kcov --bash-parser=/path/to/bash-4.3 [other args]
(With kcov, that is!)
Original comment by simon.ka...@gmail.com
on 26 Feb 2015 at 7:11
Thanks. That seems work fine (though I had to get the most recent version of
bash-4.3 (4.3.30, not 4.3.0) for it to work.
Original comment by mham...@sandia.gov
on 26 Feb 2015 at 6:41
Original issue reported on code.google.com by
hami...@comcast.net
on 4 Feb 2014 at 9:27