Re: Bash-5.2-alpha available
Unfortunately I still see clobbered history lines. When moving to a previous history line, editing it, and then invoking history-search-backward and accepting it, the editing remains on this line (as of before history-search-backward), without a way to undo it (the undo list is empty). -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: Bash regexp parsing would benefit from safe recursion limit
On 3/30/22 7:48 PM, Steffen Nurpmeso wrote: Chet Ramey wrote in : |On 3/30/22 11:16 AM, willi1337 bald wrote: |> Bash Version: 5.1 |> Patch Level: 16 |> Release Status: release |> |> Description: |> |> A deeply nested and incorrect regex expression can cause exhaustion of |> stack resources, which crashes the bash process. | |Bash doesn't use it's own regexp engine; it uses whatever POSIX regexp |functions are provided by the C library (regcomp/regexec/regfree/regerror). Once there was that ???FTP CVE regarding recursion, what they did was simply counting *'s in the expression string, and restricting it to three occasions per expression. That seems arbitrary and limiting. I'd rather see any `fix' for this kind of incorrect regexp come in the library functions themselves. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
Re: Bash-5.2-alpha available
On 3/31/22 5:14 AM, Andreas Schwab wrote: Unfortunately I still see clobbered history lines. When moving to a previous history line, editing it, and then invoking history-search-backward and accepting it, the editing remains on this line (as of before history-search-backward), without a way to undo it (the undo list is empty). So is this the scenario? If you have echo 1 echo 2 echo 3 history in your history, type ^P^P^P to get back to the `echo 2'. Add `24' to the end, type ^A^F so the cursor is after the `e', then run history-search-backward? Hit the `echo 1' and accept-line? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
Re: Bash-5.2-alpha available
On Mär 31 2022, Chet Ramey wrote: > So is this the scenario? If you have > > echo 1 > echo 2 > echo 3 > history > > in your history, type ^P^P^P to get back to the `echo 2'. Add `24' to > the end, type ^A^F so the cursor is after the `e', then run > history-search-backward? Hit the `echo 1' and accept-line? Yes. Afterwards, I see this history: 1 echo 1 2 echo 24 3 echo 3 4 history 5 echo 1 6 history -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: bug-bash Digest, Vol 232, Issue 27
I have put together my own bash debugger (I like it better than the others I've seen), and wanted to have variable name auto completion in the 'read' built-in, just like it is in the base command line. Is there a reason that bash uses a readline that is differently configured in the 'read' builtin versus the full featured autocompletion available in readline at the command line? Would this be a difficult thing to implement? -- Jeremy
