| Summary: | Regex match failure | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ville Skyttä <ville.skytta> |
| Component: | bash | Assignee: | Siteshwar Vashisht <svashisht> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | admiller, jeder, praiskup, ville.skytta |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-21 10:33:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ville Skyttä
2016-03-16 12:19:05 UTC
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. bash uses regexec() function to match regular expressions. Did you notice if the result was dependent on version of glibc that was running on the system ? Because the systems listed in the initial comment vary so much, I'm fairly certain that the version of glibc between them varies as well, and I'm not sure if FreeBSD uses glibc in the first place. But I don't have any more specific information about the differences than this. I have not been able to reproduce this bug on either Fedora Rawhide or F25 systems. As per comment 3 and comment 4, I assume this bug was caused by different versions of glibc. Redirected here by googling for 'slow bash completion for tar' with detour through the source github issue. Could this please be re-opened? I'm using a fully updated F25, and in summation this is fast: My working dir: $ ls -1 *xz file1.tar.xz file2.tar.xz $ tar xf file<tab><tab><tab> never completes $ tar -xf file<tab><tab><tab> completes immediately $ rpm -q glibc bash-completion glibc-2.24-4.fc25.x86_64 bash-completion-2.5-1.fc25.noarch It appears F25 already has the correct regex according to https://github.com/scop/bash-completion/commit/0b7189d4eee4597e11cab02e6b4dcae488db5ca8 $ grep -n blank /usr/share/bash-completion/completions/tar | grep space 108: ^[[:blank:]]{1,10}(((,[[:blank:]])?(--?([\]\[a-zA-Z0-9?=-]+))(,[[:space:]])?)+).*$ ]]; then Not reproduced on F25: $ rpm -q bash-completion bash tar bash-completion-2.5-1.fc25.noarch bash-4.3.43-4.fc25.x86_64 tar-1.29-3.fc25.x86_64 And glibc: $ rpm -q glibc glibc-2.24-4.fc25.x86_64 glibc-2.24-4.fc25.i686 Any suggestions on debugging further? Otherwise I'll just fix up my muscle memory to use tar -xf I don't have anything else besides the generic bash-completion troubleshooting instructions, see Troubleshooting in its README.md. When the Troubleshooting produces "too verbose" output, I usually edit
the completion file /usr/share/bash-completion/completions/tar manually:
- add my_debug() { echo "$*" >> /tmp/debug_info ; }
- put "my_debug info messages" on proper places
Then:
- in one terminal test the completion
- in another terminal put `tail -F /tmp/debug_info` and read the debugging
info
I am closing this bug as there has been no updates on it. Feel free to reopen if required. |