Re: pwd and prompt don't update after deleting current working directory

On Thu, Jul 11, 2024 at 7:32 PM David Hedlund wrote: (...) > I understand. So the feature request should be an option "-b" (for > bounce out of the directory when deleted) for example? > It'd be helpful to know about the use cases for such feature though. My assumptions: - This would only be u

Re: pwd and prompt don't update after deleting current working directory

On Thu, Jul 11, 2024 at 7:20 PM David wrote: (...) > Hi, I disagree, and I think if you understand better why this occurs, you > will understand why knowledgable users will disagree, and you will > change your opinion. > I concur. The requested feature changes behavior in a backwards-incompatibl

Re: String replacement drops leading '-e' if replacing char is a space

> > Description: > > If a string starts with '-e' the replacement operators ${x//,/ } and ${x/, > /} drop the '-e'. > The behaviour seems to be very specific: the string must start with '-e' > and the replacing character has to be a space. > > Repeat-By: > > x='-e,b,c' > echo ${x//,/ } > b c > echo

Re: git amend commit with backticks on cli causes tty to crash

On Fri, Jul 21, 2023 at 9:14 AM Dale R. Worley wrote: > (...) > Also, you don't state explicitly what you think the error is. I assume > you mean that "Press [ctrl-d] again and tab (tty 5) crashes." should not > be happening. > > But it looks to me like you're sending ctrl-d into a shell. That,

Re: With DEBUG trap, resizing window crashes script

On Wed, May 10, 2023 at 1:03 PM Wiley Young wrote: > (...) > The script is set up to enable the DEBUG trap and prompt. When the first > user prompt appears, in this case `set -x` although xtrace was enabled at > the crashbang, if I resize the window then press enter, the script dies and > displa

Re: bottom of ${BASH_LINENO[*]} stack is always '0'

On Tue, Feb 21, 2023 at 2:58 PM bill-auger wrote: > > the bottom of the ${BASH_LINENO[*]} stack is always '0'; and the > array never contains the line number of the actual call site, as > ${LINENO} does - is that expected behavior? > > im not sure if this is a bug or not - it seems like a bug to m

Re: Performances comparission between 5.1 and 5.2.

On Mon, Aug 15, 2022 at 10:09 AM Greg Wooledge wrote: > On Mon, Aug 15, 2022 at 07:05:49PM +0200, felix wrote: > > Description: > > Trying some script under 5.2 beta, rc1 and rc2, I was surprised by > execution time. > > Pre-release versions of bash are built with extra debugging stuff, and

Re: current bash.git.devel segfaults on my code

On Wed, Oct 20, 2021 at 3:46 AM Alex fxmbsw7 Ratchev wrote: > > it betteted up, it still segfaults without valgrind but valgrind dorsnt > show so many entries anymore > there are 3 valgrind outputs, one without -- two with ine --arg ( the > valgrind supported .. ) and three the two --opts > > the

Re: $PPID behave differently in 5.1 and 4.3

On Sun, May 16, 2021 at 1:38 AM leodream wrote: > > I created 2 scripts like below > > > Running the test1.sh with bash 5.1 will have different PPID printed by the > last test2.sh call when it is executed in sub-shell.

Re: Latest devel branch push

On Sat, May 15, 2021 at 4:54 AM Alex fxmbsw7 Ratchev wrote: > > may i ask frankly for the git cmd to get it You can find the instructions on how to clone the repository in the Savannah portal: https://savannah.gnu.org/git/?group=bash i.e. git clone https://git.savannah.gnu.org/git/bash.git

Re: incorrect character handling

On Tue, Mar 30, 2021 at 1:38 PM by.sm--- via Bug reports for the GNU Bourne Again SHell wrote: > > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: darwin18.7.0 > Compiler: clang > Compilation CFLAGS: -DSSH_SOURCE_BASHRC > uname output: Darwin Mac 18.6.0

Re: how does ssh cause this loop to preterminate?

On Wed, Mar 24, 2021 at 2:22 PM gregrwm wrote: > > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security > uname output: Linux ginger 4.18.0-240.15.1.el8_3.x86_64 #1 S

Re: the bugs on simplificied code didnt appear im sorry check up the old paste or let it be

On Tue, Feb 2, 2021 at 12:52 PM Alex fxmbsw7 Ratchev wrote: > > bash-5.1# n=1 bash ../ixz/paster desc 0 1 2 3 > ++ paste BEGIN ++ Could you at least use a standard archive format to send these, and not whatever this format is? I doubt you'll get much help when the first step is to piece together

Re: obscure bug "extern void free (void *__ptr) __attribute__ ((__nothrow__ , __leaf__));"

On Thu, Jan 21, 2021 at 2:07 PM Mathias Steiger wrote: > > > As such bugs are likely related to buffer issues, maybe even in > underlying APIs, and since they only surface after very lengthy > mysterious sequences of commands - often just on single specific system > installations - I wouldn't know

Re: obscure bug "extern void free (void *__ptr) __attribute__ ((__nothrow__ , __leaf__));"

On Thu, Jan 21, 2021 at 1:32 PM Eduardo Bustamante wrote: > > On Thu, Jan 21, 2021 at 1:28 PM Mathias Steiger > wrote: > > > > > > No. > > > > If you read the the rest of the bug report, it might become clearer to you. > > > > > &g

Re: obscure bug "extern void free (void *__ptr) __attribute__ ((__nothrow__ , __leaf__));"

On Thu, Jan 21, 2021 at 1:28 PM Mathias Steiger wrote: > > > No. > > If you read the the rest of the bug report, it might become clearer to you. > > > Suppose I wrote a simple script: > > {if echo "27ac5e2f757302" >& /dev/null; then echo "yes"; else echo > "no"; fi } > output Did you mean:

Re: echo $'\0' >a does not write the nul byte

On Sun, Jan 17, 2021 at 12:05 PM wrote: > (...) > The nul byte is not echoed by $'\0'. This is expected. Bash uses NUL-byte terminated character sequences to store strings, so it can't actually store NUL bytes themselves. $'\0' is the same as '' (i.e. an empty string). If you want to o

Re: Bash Reference Mamual

On Sat, Oct 17, 2020 at 3:48 PM Craig H Maynard wrote: > Hi, > > In section 3.5.4 "Command Substitution", the following sentence may have a > typo: > > > The command substitution $(cat file) can be replaced by the equivalent > but faster $(< file). > > > My proposed change: > > > The command subs

Re: looking for consistent C-c trap behavior

On Fri, Apr 17, 2020 at 1:09 PM Greg Wooledge wrote: > > On Fri, Apr 17, 2020 at 01:02:20PM -0700, Eduardo Bustamante wrote: > > On Fri, Apr 17, 2020 at 12:59 PM gentoo_eshoes--- via Bug reports for > > the GNU Bourne Again SHell wrote: > > > > > > I'v

Re: looking for consistent C-c trap behavior

On Fri, Apr 17, 2020 at 12:59 PM gentoo_eshoes--- via Bug reports for the GNU Bourne Again SHell wrote: > > I've noticed that if I trap SIGINT in a bash script, the behavior when > encountering C-c depends on whether an external command (eg. 'sleep 100') or > a builtin command (like 'read -p') w

Re: First lines of examples/startup-files/bashrc

On Wed, Apr 8, 2020 at 2:42 PM Martin Schulte wrote: (...) > But, as far as I understand, a non-interactive bash doesn't read > ~/.bashrc at all - so shouldn't we just omit them? There are exceptions. One of them being SSH, see: https://git.savannah.gnu.org/cgit/bash.git/tree/shell.c?h=ea31c00845

Re: Seg history

On Tue, Oct 22, 2019 at 6:09 AM younes berramdane wrote: > > Hello, > I have found a seg in the history of bash while I was doing a project for my > school, > (Put fc -s at the last command of the history file [~/.sh_history] for bash > posix or [~/.bash_history] for bash then launch bash and ex

Re: Disable microsoft telemetry

On Sun, Oct 20, 2019 at 4:55 AM Gerard E. Seibert wrote: > > On Fri, 18 Oct 2019 18:17:27 +0330, Behrooz Amoozad stated: > >I'm not sure if this even fits here, but it would be really nice if the > >default bashrc included DOTNET_CLI_TELEMETRY_OPTOUT='true'. > >Currently, After installing microsof

Re: Wrong explanation of getopts

On Sun, Sep 15, 2019 at 12:58 PM Roland Illig wrote: > > The help text of getopts says: > > > Getopts normally parses the positional parameters ($0 - $9), but if > > more arguments are given, they are parsed instead. (...) > The "instead" in "they are parsed instead" is totally wrong. $1 to $9

Re: Incorrect passing of argc argv with multiple redirects

On Tue, Jul 30, 2019 at 10:35 AM Morgan McClure wrote: (...) > ./a.out foo > /dev/null 2&>1; echo $? > returns 3 NOT as expected Are you 100% certain the `2&>1` redirection means what you think it means? (hint: I recommend reading the "Redirecting Standard Output and Standard Error" section o

Re: alias problem -- conflict found

Can we please STOP this thread? What is the point? Linda will never change her mind. You all are just wasting time and electricity. (and spamming the mailing list with this non-sense).

Re: building bash 5.x problems+coredumps

On Mon, Jul 8, 2019 at 3:44 PM L A Walsh wrote: > > This hasn't worked for me yet, that I remember. Some of itt may be in some > library I'm linking, but not sure what might be causing the problem. Can you provide more information about your environment? - Compiler & version version - "configur

Re: Using Source within Binary Shell Scripts

On Wed, Mar 27, 2019 at 8:17 AM Jason Hall wrote: (...) > The point is, their is a legitimate use for sourcing Binary Shell > Scripts (...) Is it really a legitimate use? If you're doing it for "security" (by obscurity I guess?), it's easy to defeat. > and BASH as is, won't let you do this. May

Re: General Associative Array problem -- Was: UUID as Array Keys strangely not possible

On Fri, Feb 22, 2019 at 3:24 AM Robert White wrote: (...) > tail --lines=+3 /proc/partitions | grep -v ram | > while read -a RECORD > do (...) > eval [${INLINE[UUID]}]=boo (...) > done > > echo " Keys: " "${![@]}" = "${[@]}" > echo " Keys: " "${![@]}" = "${[@]}" >

Re: bug: illegal function name?

On Sun, Jan 20, 2019 at 11:05 AM Andrey Butirsky wrote: > > Eduardo, the question is about inconsistent, error-prone implementation. > Not about the workarounds. What's the error prone part? - Declare a function name - Unset it with 'unset -f'

Re: bug: illegal function name?

On Sun, Jan 20, 2019 at 10:46 AM Andrey Butirsky wrote: > > I'm not quite understand what exactly is "intentional". Accepting different sets of function names (when POSIX mode is either on/off). > The problem is inconsistent behavior of unset '-f' flag for "normal" and > "not-normal" function na

Re: Sourcing a script from a pipe is not reliable

On Wed, Jan 9, 2019 at 10:54 PM Jeremy wrote: (...) > 3.2.57(1)-release (x86_64-apple-darwin15) > > > This is on MacOS 10.11.6. If there is a better place for me to report this > bug, please let me know. Have you tried the latest version? Bash 5.0 was just released: https://lists.gnu.org/archive/

Re: Probable recursion in particular alias

On Wed, Jan 9, 2019 at 4:59 AM Ante Perić wrote: (...) > Description: > Having an alias of type: > alias bug="\ >echo \"no output, 100% cpu\" \ > " > in .bashrc will give no output, will not complete, and it will peg the CPU to > 100%. Can you share the output of (right aft

Re: $RANDOM not Cryptographically secure pseudorandom number generator

On Sat, Jan 5, 2019 at 12:12 PM Eduardo A. Bustamante López wrote: (...) > 2. Performance impact > > The new RNG does more work, and thus, it is expected to have a performance > impact when generating lots of random numbers. I tested 3 systems (2 amd64 > and 1 > armhf) and include the results bel

Re: Identical function names in bash source code

On Sat, Jan 5, 2019 at 11:38 AM Peng Yu wrote: > > > What would you say the "suggested improvement" is here? > > This is implied. If it is agreed that identical function names are not > good by the majority of bash developers, then what I found could be > turned into an explicit suggestion. > > Si

Re: Identical function names in bash source code

On Sat, Jan 5, 2019 at 10:25 AM don fong wrote: > > for my 2c, the post seems within the charter. > > quoting from the bug-bash info > page: > > > This list distributes, to the active maintainers of BASH (the Bourne Again > > SHell), bug reports and

Re: [Help-bash] How to run tests/?

On Tue, Jan 1, 2019 at 10:09 PM Eduardo Bustamante wrote: > > On Tue, Jan 1, 2019 at 9:42 PM Eduardo Bustamante wrote: > > > On Tue, Jan 1, 2019, 8:46 PM Peng Yu, wrote: > >> > >> I got the following errors when I try tests/ in the bash source code. > >&g

Re: Should [[ -v 1 ]] be supported?

On Thu, Dec 27, 2018 at 9:45 PM Peng Yu wrote: (...) > Yes and no. For a particular bash script, you can quantify which bash > features are the most time-consuming. (...) > (...) But you can not profile all the > bash scripts that have ever been written. Since there are only limited > features in

Re: Should [[ -v 1 ]] be supported?

On Thu, Dec 27, 2018 at 5:38 PM Peng Yu wrote: > > > I don't believe that at all. The number of positional parameters is kept > > anyway. It's not recalculated when you compare it to another number, so > > it's just as fast as a simple comparison of two integers. > > Getting the number $# is slow.

Re: How to compile hashlib.c for testing?

On Thu, Dec 27, 2018 at 5:15 PM Peng Yu wrote: (...) > Since the main() function is already there, why there is not already > an easy way to compile it? How do you do unit-testing then for the > code? This is very easy to figure out from the source code, right :)? (Hint: there is no "unit" testi

Re: Should [[ -v 1 ]] be supported?

On Thu, Dec 27, 2018 at 4:50 PM Peng Yu wrote: (...) > What I meant in my original email is that I want something for testing > if there is a command line argument (one or more, the exact number > does not matter). $# gives more than that info, because it tells not > only whether is any command li

Re: write() not retried after EINTR in printf and echo

On Tue, Dec 25, 2018 at 12:01 PM Bize Ma wrote: (...) > But, probably, I should just not inform you of what others think given your > upfront rejection to any (constructive) criticism. (..) > Do as you wish, we will still be able to form our own opinion about buggy > code. This is not constructiv

Re: Bash build issues in `devel' branch due to -Werror compiler flag

On Mon, Dec 17, 2018 at 6:31 AM Chet Ramey wrote: (...) > Good. This is the kind of feedback I want from enabling this option during > the pre-release period. Thanks for taking the time. Thank you! Bash `devel' builds fine for me now.

Re: Memory continusely increase

+ Adding Abhishek Hi Chen and Abhishek, it seems you might work on the same team since you sent the exact same bug report: - http://lists.gnu.org/archive/html/bug-bash/2018-12/msg00059.html - http://lists.gnu.org/archive/html/bug-bash/2018-12/msg00058.html - http://lists.gnu.org/archive/html/bug-

Re: $RANDOM not Cryptographically secure pseudorandom number generator

On Sat, Dec 15, 2018 at 6:08 PM Ole Tange wrote: (...) > But your comment actually emphasizes my point: We _will_ have users > who are naive enough to use $RANDOM in ways you and I would not do, > because we know it is unsafe. > > Let's make those usages a little safer. You know no one is stoppin

Re: $RANDOM not Cryptographically secure pseudorandom number generator

On Mon, Dec 3, 2018 at 9:36 AM Greg Wooledge wrote: > > On Mon, Dec 03, 2018 at 05:31:18PM +0100, Ole Tange wrote: > > Luckily I did not just assume that Bash delivers high quality random > > numbers, but I read the source code, and then found that the quality > > was low. I do not think must user

Re: $RANDOM not Cryptographically secure pseudorandom number generator

On Sun, Dec 2, 2018 at 3:14 PM Ole Tange wrote: (...) > Git's use of SHA1 seems to be a prime example of what can go wrong: > https://shattered.io/ What does a PRNG have to do with a hashing function? > Can you elaborate on why you think it is a bad idea to change an > insecure PRNG into a non-b

Re: Indices of array variables are sometimes considered unset (or just display an error).

On Mon, Nov 5, 2018 at 6:01 PM Great Big Dot wrote: (...) > > [... A]ccessing the index list of multiple-element arrays > > fails when you append the unset expansion. With single-element > > arrays, it fails iff the element in question contains any special > > characters or whitespace, and thinks

Re: [BUG] Bad call to dircolors in /etc/bash.bashrc on LMDE

On Wed, Oct 31, 2018 at 9:52 PM Philip Hudson wrote: (...) > Description: > At line 44 of /etc/bash.bashrc the line > >eval $(dircolors) > > is incorrect: it errors if $SHELL is tcsh. All other calls correctly > specify 'dircolors -b'. > > Note: Arises on Linux Mint Debian Edition 2. I have no

Re: Use-After-Free in Bash

On Tue, Oct 30, 2018 at 1:03 PM Corbin Souffrant wrote: (...) > I found a reproducible use-after-free in every version of Bash from > 4.4-5.0beta, that could potentially be used to escape restricted mode. I > say potentially, because I can get it to crash in restricted mode, but I > haven't gone t

Re: Auto-update program cache feature

On Wed, Oct 3, 2018 at 11:20 PM Jeffrey Walton wrote: (...) > How Bash achieves it is an implementation detail left to the experts. > I made a few suggestions that don't seem to fit well. That's OK > because Bash internals is not my area of expertise. I think it's important to always consider the

Re: Local Privilege Escalation

On Wed, Sep 26, 2018 at 4:27 PM cjoke wrote: > > Hi, is there a bounty bug program for Bash? AFAIK, there isn't. If you found a security vulnerability in bash, please make sure to disclose it privately to Chet (chet.ra...@case.edu) instead of this public mailing list.

Re: [bug-bash] Which commit for a bug in 4.3.48 which is fixed in 4.4.23

On Mon, Sep 24, 2018 at 4:09 AM Dr. Werner Fink wrote: (...) > Reconstructed the attached patch ... seems to work Out of curiosity, what problem are you trying to solve?

Re: Bash-5.0-alpha available

On Wed, May 23, 2018 at 12:55 PM Chet Ramey wrote: > > The first alpha release of bash-5.0 is now available with the URL > > ftp://ftp.cwru.edu/pub/bash/bash-5.0-alpha.tar.gz > > and from the bash-5.0-testing branch in the bash git repository > (http://git.savannah.gnu.org/cgit/bash.git/log/?h=bas

Re: expand_prompt_string segmentation faults

On Sat, Sep 15, 2018 at 8:15 PM Chet Ramey wrote: (...) > Thanks for the report. They are the same problem. Thanks Chet. Do you have a patch for the issue? I have a few other cases but I'm not sure if they're all due to the same cause.

Re: Assignment of $* to a var removes spaces on unset IFS.

On Mon, Aug 13, 2018 at 5:25 PM Robert Elz wrote: [...] > What's more, reporting bugs in bash 4.3 is just a waste of everyone's time. > Upgrade to (at least) the current released version, and use that instead. Adding to this point: * bash 4.3 was released 4 years ago (2014-02-26) * bash 4.4 is t

Re: Number with sign is read as octal despite a leading 10#

On Tue, Jul 10, 2018 at 1:57 PM, Isaac Marcos wrote: > Chet Ramey () wrote: [..] > This is not a serious argument. [...] > I don't care. All other shells do this correctly. It makes you the only one > wrong. > > This is not a serious discussion. Can you keep the discussion civil? I don't get why

Re: announcing bashj

://fil.gonze.org/wikiPG/index.php/Project_bashj_:_a_bash_mutant_with_java_support>* >- *http://fil.gonze.org/wikiPG/index.php/Bashj_programming_guide ><http://fil.gonze.org/wikiPG/index.php/Bashj_programming_guide>* > > > On 23/06/18 20:45, Eduardo Bustamante wrote: > > On Sat, Jun 23,

Re: announcing bashj

On Sat, Jun 23, 2018 at 12:08 PM, pg wrote: [...] > Description: BASHJ - ANNOUNCE TO THE DEVELOPMENT TEAM OF BASH > > I am pleased to inform you about bashj - a bash 'mutant' with java > support. > This product opens numerous very interesting fields to bash developers. I have a few questi

Re: [PATCH] A terminating signal has to complete a bash process

It's in commit 96b7e26874047647e85bd5c7e71a7f664174c2cc, in the `devel' branch of the git repository. On Mon, May 21, 2018 at 12:42 AM, Andrei Vagin wrote: > Hello Chet, > > Have you had a chance to try this patch? Let me know if you will have > any questions. > > Thanks, > Andrei > > On Thu, May

Re: PDF documentation output not readable (3.2.6 GNU Parallel)

El jue., may. 10, 2018 11:11 AM, Greg Wooledge escribió: > [...] > > from Section 3.2.6 GNU Parallel > > GNU parallel is a separate project from GNU bash. You'll want to > report the bug to the GNU parallel tracker, at > or whatever email > equival

Re: bash shows an error message about unpaired quotes, but they are paired

On Mon, Mar 26, 2018 at 1:54 PM, wrote: [...] > run 'sed -i "6a\find /srv/cowrie/log/ -mtime +7 -name \'cowrie.*\' -delete" > cowrietest' That's not how you escape single quotes within single quotes. Read: https://mywiki.wooledge.org/Quotes#Types_of_quoting The proper way would be: run 'sed -i

Re: ${parameter/pattern/string} behaviour changed

On Fri, Mar 16, 2018 at 1:18 PM, wrote: [...] > Bash Version: 4.3 > Patch Level: 42 > Release Status: release > > Description: > Command: x="a b c"; echo "'${x// /','}'" > On old systems the output is: 'a','b','c' > In this version the output is: 'a,b,c' > This ne

Re: Strange/incorrect behavior of a fake executable file

(I've added bug-bash again) On Tue, Mar 13, 2018 at 11:32 PM, Vladimir Likic wrote: > Thanks for the quick response! > Your are correct, "." was in PATH (my bad), an it's calling itself > recursively. That went into a spiral and crashed the computer (literally). > Why is bash actually executing

Re: Strange/incorrect behavior of a fake executable file

On Tue, Mar 13, 2018 at 7:24 PM, Vladimir Likic wrote: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-lin

Re: Avoiding file-based constraints for tmp files (ws Re: [minor] umask 400 causes here-{doc,string} failure)

On Mon, Mar 12, 2018 at 2:05 PM, L A Walsh wrote: [...] > What would be the downside(s) of such an implementation? There's code out there that relies on several properties of regular files, one of them for example, that you can seek on them. I recommend against any change to here documents and he

Re: Heap buffer overread in token_is_assignment

On Tue, Feb 20, 2018 at 2:07 PM, wrote: > > > > > Configuration Information [Automatically generated, do not change]: > Machine: i686 > OS: linux-gnu > Compiler: afl-gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'

Re: bug-bash

On Thu, Feb 8, 2018 at 4:23 PM, Nolan <4030...@gmail.com> wrote: > I have found a 'result' of a command that cannot be a feature. > > Enter command, command executes, prints exit at the prompt. > > Goes to next line in terminal showing the "#" prompt. > > A "whoami" says root. > > Is this known? >

Re: xmalloc crash

On Mon, Jan 8, 2018 at 8:22 AM, Chet Ramey wrote: > On 1/6/18 2:40 PM, Eduardo A. Bustamante López wrote: > >> So the allocation fails, even if the system has enough memory to handle it. >> Upon closer inspection: >> >> dualbus@ubuntu:~/src/gnu/bash/lib/malloc$ cat -n malloc.c | sed -n >> '77

Re: Use of --rcfile does not preclude read of /etc/bash.bashrc

On Tue, Jan 2, 2018 at 3:05 PM, Nat! wrote: [...] > Description: > The documentation states, that /etc/bash.bashrc should not be read > (rightfully so IMO) with > --rcfile. FWIW, there are two things going on here: (1) /etc/bash.bashrc is actually disabled by default in the upstream bash

Re: Bash: sleep execution issue with bash loadable builtins

On Mon, Dec 4, 2017 at 5:08 AM, Thiruvadi Rajaraman wrote: > Hi Chester, > > Based on your review comments and suggestions about the earlier fixes, > reworked on the fix with pselect() > to block the signal. FYI, Chet pushed a few changes related to this in commits 564452a3ec9b73a53949325cc4acb9

Re: [PATCH] Fix hang if $OLDPWD points to inaccessible directory

On Mon, Nov 27, 2017 at 6:00 PM, Mikulas Patocka wrote: [...] > Will you commit my patch? - if you agree with it. Hi Mikulas. Chet is the one and only bash maintainer, you'd have to convince him. As a bystander that happens to be interested in bash's development, I agree with your points, but ex

Re: umask builtin

On Wed, Nov 8, 2017 at 10:06 AM, kalle wrote: [...] >> From umask(1p): >> For a symbolic_mode value, the new value of the file mode creation mask >> shall be the logical complement of the file permission bits portion of >> the file mode specified by the symbolic_mode string. > > This senten

Re: Potential Denial of Service Vulnerability in embedded commands - Bash version 4.4.12(1) - Release

On Tue, Nov 7, 2017 at 5:58 AM, Alex Nichols wrote: [...] > In order to trigger the bug I executed the command *`*cat sploit.buf*`* > where sploit.buf is a just over 2GB file of ‘A’ characters. When this > command is executed the bash terminal crashes with the following error > “Bash: xrealloc: ..

Re: help complete: mention remove all AND restore all

On Sun, Nov 5, 2017 at 7:01 PM, 積丹尼 Dan Jacobson wrote: > OK, please on > $ help complete > at "-r" please mention > "To instead toggle on and off PROGRAMMABLE completion, use shopt -[su] > progcomp." > > Reason: there is very little chance the user could Google the right > answer out of the fore

Re: New MILLISECONDS “special” variable?

El mié., nov. 1, 2017 8:48 PM, Eduardo A. Bustamante López < dual...@gmail.com> escribió: > [...] > /* FIXME: do better validation */ > static int parse_timeval (const char *s, struct timeval *tv) { > char *ds; > timerclear(tv); > tv->tv_sec = strtol(s, &ds, 10); > if (ds && *ds == '.') {

Re: 'fc' outputing text of DEBUG trap

On Fri, Oct 27, 2017 at 1:21 AM, Boruch Baum wrote: > In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap > in my .bashrc and tried running the following command, with the > following output resulting. The five lines between the command being run > by fc and that command's outp

Re: Simple sleep scripts causes SEGFAULT

On Wed, Oct 25, 2017 at 11:21 PM, Alex Coffin wrote: [...] > Description: > Segmentation fault. I'm honestly not sure why. I was using batsh to > make a simple script. When I ran it generated a segfault. The segmentation > fault DOES NOT occur if "sleep" is replaced with "echo". > I also r

Re: Bash should reset OLDPWD upon login, *only*.

On Tue, Oct 3, 2017 at 5:01 PM, L A Walsh wrote: [...] Ah, because you can't protect against everything, you leave your system > open with no passwords on the logins? What's your system name again? :-) Linda. This topic has no relation at all with the reported issue, and we're doing a disser

Re: Declared Var Dynamic Initialization = No Return Code Back?

On Tue, Sep 12, 2017 at 5:04 PM, Adam Danischewski wrote: [...] > Declaring a variable doesn't seem risky enough to eat up the return code. > Is there a reason for this? I doubt that it would break anything to change. > It's a lot more intuitive and syntactically streamlined to check for > missing

Re: 'time' doesn't time subshells that exec

On Sat, Sep 9, 2017 at 5:16 AM, Martijn Dekker wrote: > The 'time' reserved word seems to be unable to time subshells that run > 'exec'. Is this intentional? (ksh93, mksh and zsh all do manage this.) As far as I know, it is intentional. Read this thread which is about a similar issue: https://lis

Re: Bug in select-command

On Sat, Jun 24, 2017 at 9:46 AM, Eduardo A. Bustamante López wrote: [...] > For some reason though, the following fails to update the value of COLUMNS: [...] > echo \$- $- > echo cols $(tput cols) > command true # this should trigger? > select opt in "${options[@]}"; do > break > don

Re: bash sigabrt

On Tue, Jun 20, 2017 at 9:12 AM, Rajaa, Mukuntha (Nokia - IN/Bangalore) wrote: > Hi, > > Bash-4.4.12(1) release occasionally coredumps. This was tested on mips64 > platform. Could you please confirm, is this a known bug or should I raise a > ticket for this ? This error means that bash's intern

Re: Read builtin -e (readline) oddities

On Mon, Jun 19, 2017 at 9:57 AM, Eduardo A. Bustamante López wrote: [...] > Hm, I can still reproduce it under Debian 9, using the `devel' branch, and I'm > sure no startup files are being sourced. > > dualbus@debian:~/src/gnu/bash-builds/devel$ ./bash --norc --noprofile > bash-4.4$ declare -p

Re: Why does 'connect' take so long (sometimes) and can't be interrupted?

On Thu, Jun 15, 2017 at 10:36 AM, wrote: [...] > Description: > This is a little complicated and I can't give you full details on how > to > replicate it, since I don't fully understand it myself. But under > certain > circumstances, the following line takes a very long

Re: cygheap base mismatch detected

On Thu, Jun 15, 2017 at 1:19 PM, Eduardo Bustamante wrote: [..] > Please report this to the Cygwin folks. This is not a bash issue. Err, not the Cygwin folks. You seem to be using Cmder, so ask them.

Re: cygheap base mismatch detected

On Thu, Jun 15, 2017 at 11:30 AM, Jon Morris wrote: > Hi, > > Just tried to submit a bug, but bashbug command failed, so here is the > problem text. > > Thanks, > > Jon Please report this to the Cygwin folks. This is not a bash issue.

Re: Patch for unicode in varnames...

(_("%s has null exportstr"), v->name); return (0); } + /* XXX: Update */ if (legal_variable_starter ((unsigned char)*s) == 0) { internal_error (_("invalid character %d in exportstr for %s"), *s, v->name); @@ -4418,6 +4419,7 @@ valid_exportstr (v) { if (*s == '=') break; + /* XXX: Update */ if (legal_variable_char ((unsigned char)*s) == 0) { internal_error (_("invalid character %d in exportstr for %s"), *s, v->name); -- Eduardo Bustamante https://dualbus.me/

AddressSanitizer: heap-buffer-overflow in shell_expand_line

fe4kJDVTPCT0JADrl5eq l5eXl5eXl5eXl5eXdJeXZECXl+vr6+uAfyIbG2OA+QUFBQUFJBsbY4AQBQUFBQUkfwUF BQUFBQUFBQUFBQCTFAAkKAAbBQ== -- Eduardo Bustamante https://dualbus.me/

AddressSanitizer: heap-buffer-overflow in rl_kill_text

UVFRT5FRUVFRRkFQgQOBs4Exgo OBs4ExgYKDgbGAAABgEnKGEdAgAbOBMVFeEVFRUVFRT5FQgQOBs4ExgoOBs4ExgmABs4ExgoOBs4 ExhlGAAABhgn9wAmYR0CABs4ExgoOBs4ExgQEAsQEDMQGzgTGEX3ABAAANwQIEUYZAAGABDbABAA ABjEAj9ADjs= -- Eduardo Bustamante https://dualbus.me/

AddressSanitizer: heap-buffer-overflow in rl_search_history

PgAAACwMAAABAEhIBj48yAP//8H+A/9h/gM4SEjMDEhISAxISEhMS EgMA/xLMzACA//8BAMyAHf0AgADOEhIzAxISEgMSEhITEhIDAP8SzMwAgP//AQDMgB397cAQ 6BISExISzMx/jxwAdIASEhIDEh8gAxISAY+PAAD///+dgM4SEhISEgCd9gASEgMBGxI0LRIT gI8DAH9Xj2SPjhISEun//xKDj4+PjwIKIg== -- Eduardo Bustamante https://dualbus.me/

AddressSanitizer: global-buffer-overflow in rl_filename_completion_function

48i6sB//9/YEAA AAMbGTw8PDw8VP8BGxlgBHt7e3t7e3sQlvwAcQ7/IuAMFBAbGxsrAKEBAJqampqSljyAFH8bGxlU 9t7XllMkLZYAABAgUxP6GhveLwCV/ZYQGxsb/3///yR7e3t7e94vFAAA//8bKgCh8QJ///IbkCEk +iADVP8bG28AGwIbUyQoeRv/GvpAFJQABAIbU+KVG1QE3iYUvxQbGwAC/VMbLxtUBBsbAAL9Uxsv G1QEGxsbG1QAQCsAl+2WEBsbGwobFJYUGxsbSAAAQAAAg+2WEBsbGwrqdwAR+nx8YoB/aNkDMmRR UVFR/fwAdgQbAhtdGxsfAIAUAACiEPwAlgQbAv1TGxUbABsbGVT//3//lgTelhQbGht7e/ogA1T/ GxtTJAp5G/8aDBSUAAR7/3t7e/oMFJQABHt7e3u/3hEUlhQbGxsqAKEUAoAAGxsbOBsfGxsE/+0F -- Eduardo Bustamante https://dualbus.me/

AddressSanitizer: heap-buffer-overflow in rl_tilde_expand

GVY8KCooKCgoKCgoKCgo KCgoKCgoHR4eHhgxnGA8Iz0L3d3d3d3d3d3d3d3d8t3d3d3d3d3d3d3d3d3d3d3dIAABfQQyY/wZ ENobBQ== -- Eduardo Bustamante https://dualbus.me/

AddressSanitizer: heap-buffer-overflow in rl_delete

UlJSUlJS UlJSUlJSUlJSUlJSUlJSUlJSbvIbBQ== -- Eduardo Bustamante https://dualbus.me/

Re: AddressSanitizer: heap-buffer-overflow _rl_find_prev_mbchar_internal / expand_prompt

On Tue, Jun 13, 2017 at 04:30:23PM -0400, Chet Ramey wrote: [...] > I can't reproduce it with asan or without on Mac OS X. I'll look around > for a Linux system with asan to run it on. All these inputs seem to trigger the same problem. You'll find the stacktrace as reported by ASAN first, and then

Re: AddressSanitizer: heap-buffer-overflow _rl_find_prev_mbchar_internal / expand_prompt

On Tue, Jun 13, 2017 at 3:30 PM, Chet Ramey wrote: [...] > I can't reproduce it with asan or without on Mac OS X. I'll look around > for a Linux system with asan to run it on. I had to use these exact same environment variables, otherwise the out of bounds read wouldn't happen. I'm not sure if it

AddressSanitizer: heap-buffer-overflow _rl_find_prev_mbchar_internal / expand_prompt

\374\027\374\377:P\356SS輀)\027\374\027\374\027\374\027\374\377:P\356SS輀)\027\374\027\374\027\374\027\374\377:P\356SS輀", '\276' , seed=85, find_non_zero=0) at ../../../bash/lib/readline/mbutil.c:162 162 length = strlen(string); -- Eduardo Bustamante https://dualbus.me/

Re: Buffer corruption when the terminal is resized.

different shell? (zsh, mksh, dash, ksh93). -- Eduardo Bustamante https://dualbus.me/

Re: Multiline commands do not survive history -w/-r

t;%s" dualbus@debian:~$ echo 'a > b > c' a b c dualbus@debian:~$ history -w dualbus@debian:~$ history -c; history -r; HISTTIMEFORMAT= history 1 declare -p HISTFILE HISTTIMEFORMAT 2 echo 'a b c' 3 history -w -- Eduardo Bustamante https://dualbus.me/

Re: A background ssh can take over the tty from bash?

On Mon, Jun 12, 2017 at 10:24:38AM +0800, Clark Wang wrote: [...] > I've checked the ssh process and it does not catch SIGTTIN and that's why > I'm confused. Even if that were the case, what makes you think this is a bash bug? Bash is not responsible for misbehaving c

  1   2   3   >