Re: Compiling bash statically in 4.2/4.3/4.4 with GCC 6.1.0

2017-05-12 Thread Chet Ramey
On 5/12/17 9:55 AM, Eduardo Bustamante wrote: > FWIW, I'm able to compile bash statically with: > > dualbus@debian:~/src/gnu/bash$ ./configure --enable-static-link > --without-bash-malloc > [...] > dualbus@debian:~/src/gnu/bash$ make > [...] During which you get a million warnings about using any

Re: Bash stays in the secondary prompt (PS2) after completing a command with `edit-and-execute-command'

2017-05-12 Thread Chet Ramey
On 5/12/17 10:44 AM, Eduardo Bustamante wrote: > But other than that, I can't find any reference from POSIX that > mandates that the edit line must be restored after running the `v' > command. Because it doesn't say the equivalent of "execute the current command line" (as newline does), it's a st

Re: Bash doesn't handle C with acute accent properly during readline's rl_change_case

2017-05-12 Thread Chet Ramey
On 5/11/17 8:56 AM, Eduardo Bustamante wrote: > The C with acute accent character: https://en.wikipedia.org/wiki/%C4%86 > > - Upper case > dualbus@debian:~$ printf '\U0106\n' > Ć > > - Lower case > dualbus@debian:~$ printf '\U0107\n' > ć > > Now, in bash, if you type in ć, then run readline `upc

Bash segmentation fault in readline's update_line

2017-05-12 Thread Eduardo Bustamante
dualbus@debian:~/bash-fuzzing/read-readline$ base64 update_line 秧秧秧 MBs4MOenpzAwMDAwMDAwMBs4OOenpwESGQ== Core was generated by `/home/dualbus/src/gnu/bash/bash -c read -e'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-

Re: unalias works weirdly inside an if-then block

2017-05-12 Thread Gabor Burjan
On Fri, May 12, 2017 at 09:10:07AM -0400, Greg Wooledge wrote: > On Fri, May 12, 2017 at 02:33:06PM +0200, Gabor Burjan wrote: > > unalias works weirdly inside an if-then block > > Because bash has to parse the entire compound command (the entire > multi-line command up to "fi") before it can b

Re: Bash stays in the secondary prompt (PS2) after completing a command with `edit-and-execute-command'

2017-05-12 Thread Eduardo Bustamante
On Fri, May 12, 2017 at 9:44 AM, Eduardo Bustamante wrote: [...] > - dash (compiled with libedit support): If you type then > return, then ESC-v, it will open the editor on an empty file, and... > well, it nothing of what it does really makes sense. [...] > - NetBSD's /bin/sh: if you run the `v'

Re: Bash stays in the secondary prompt (PS2) after completing a command with `edit-and-execute-command'

2017-05-12 Thread Eduardo Bustamante
On Fri, May 12, 2017 at 8:35 AM, Chet Ramey wrote: [...] > The command is executed in a separate context, exactly the same as > running fc on a command from the history file (in fact, that's what > happens). It's meant to not affect the contents of the current > command line. That's how Posix spe

Re: Compiling bash statically in 4.2/4.3/4.4 with GCC 6.1.0

2017-05-12 Thread Eduardo Bustamante
FWIW, I'm able to compile bash statically with: dualbus@debian:~/src/gnu/bash$ ./configure --enable-static-link --without-bash-malloc [...] dualbus@debian:~/src/gnu/bash$ make [...] dualbus@debian:~/src/gnu/bash$ file bash bash: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically

Re: Bash stays in the secondary prompt (PS2) after completing a command with `edit-and-execute-command'

2017-05-12 Thread Chet Ramey
On 5/12/17 8:42 AM, Eduardo Bustamante wrote: > This issue came up in the following help-bash thread: > http://lists.gnu.org/archive/html/help-bash/2017-05/msg1.html > > Write: then hit return. Bash will output the secondary > prompt, because it expects the user to close the single quote. Run

Re: unalias works weirdly inside an if-then block

2017-05-12 Thread Gabor Burjan
On Fri, May 12, 2017 at 08:11:35AM -0500, Eduardo Bustamante wrote: > On Fri, May 12, 2017 at 7:33 AM, Gabor Burjan wrote: > [...] > > Description: > > unalias works weirdly inside an if-then block > > It's not just an if-then block. It's any kind of block: > [...] > > (the key part here

Re: unalias works weirdly inside an if-then block

2017-05-12 Thread Greg Wooledge
On Fri, May 12, 2017 at 02:33:06PM +0200, Gabor Burjan wrote: > unalias works weirdly inside an if-then block Because bash has to parse the entire compound command (the entire multi-line command up to "fi") before it can begin execution of it. > alias cp='cp -i' > > if [[ 1 = 1 ]]; then >

Re: unalias works weirdly inside an if-then block

2017-05-12 Thread Eduardo Bustamante
On Fri, May 12, 2017 at 7:33 AM, Gabor Burjan wrote: [...] > Description: > unalias works weirdly inside an if-then block It's not just an if-then block. It's any kind of block: dualbus@debian:~$ bash alias + shopt -s expand_aliases + alias 'x=echo x' + echo x x

unalias works weirdly inside an if-then block

2017-05-12 Thread Gabor Burjan
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-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/local/sha$ un

Re: Bash stays in the secondary prompt (PS2) after completing a command with `edit-and-execute-command'

2017-05-12 Thread Eduardo Bustamante
On Fri, May 12, 2017 at 7:42 AM, Eduardo Bustamante wrote: [...] > Bash is still in `parse_matched_pair'- This *seems* to fix it, but I actually have no clue if this is correct, or if more cleanup is required prior to the longjmp. I also removed `rl_forced_update_display ()', because otherwise Ba

Bash stays in the secondary prompt (PS2) after completing a command with `edit-and-execute-command'

2017-05-12 Thread Eduardo Bustamante
This issue came up in the following help-bash thread: http://lists.gnu.org/archive/html/help-bash/2017-05/msg1.html Write: then hit return. Bash will output the secondary prompt, because it expects the user to close the single quote. Run `edit-and-execute-command' to fix the input (e.g. ). Ba