Re: No such file..?

Thanks for looking into this. I guess this shows it isn't always helpful to just pass down error messages. Bash knows it's trying to execute something. It doesn't work out. For the naive user of a shell, it would be more helpful to have it come back with: Couldn't execute ... Because the problem i

Re: No such file..?

On Fri, May 5, 2017 at 7:44 PM, Peter Passchier wrote: [...] > The output from bash is misleading. The file is there. Couldn't the > error message be more descriptive of what's the actual problem? Bash has no way of knowing what the problem is. Bash will do: execve("...") to the binary you prov

Re: No such file..?

What I should have clarified: - This is on Linux - I am not concerned with the binary not working, but I think the error message is unclear and misleading. $ ldd /home/pp/bin/caddy /home/pp/bin/caddy: error while loading shared libraries: /usr/lib/x86_64-linux-gnu/libc.so: invalid ELF header $ st

Re: Racing condition leads to unstable exit code

It works perfectly on v4.4. Thanks! Em sex, 5 de mai de 2017 às 12:09, Chet Ramey escreveu: > On 5/4/17 3:05 PM, Chet Ramey wrote: > > >> Would the fix be backported to stable? > > > > Let me see if I can put together a patch for you to test. > > -- > ``The lyf so short, the craft so long to ler

Re: Racing condition leads to unstable exit code

On 5/4/17 3:05 PM, Chet Ramey wrote: >> Would the fix be backported to stable? > > Let me see if I can put together a patch for you to test. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@c

Re: Bash parser segmentation fault

On 5/3/17 10:29 PM, Eduardo Bustamante wrote: > On Wed, May 3, 2017 at 9:40 AM, Eduardo Bustamante wrote: > [...] > > Here are more cases, which seem to just be variations that trigger the > same bug on different paths: It's all the same path. -- ``The lyf so short, the craft so long to lerne.

Re: double free or corruption read builtin

I'm not sure if this one is related or a separate bug: dualbus@debian:~$ ~/src/gnu/bash/bash -c 'read -rN3 IFS; read' <<< $'\001\$\\' = ==5485==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60b0a1cf at pc 0x555ed4236d

Re: No such file..?

> Am 05.05.2017 um 05:57 schrieb Peter Passchier : > > I downloaded a Solaris binary and I was wondering whether I could get it > to execute with the --version commandline argument (it worked for an > arm7 binary before). But that's not what concerns me. > > $ /home/pp/bin/caddy --version > -bas

Re: No such file..?

On Fri, May 05, 2017 at 10:57:34AM +0700, Peter Passchier wrote: > $ /home/pp/bin/caddy --version > -bash: /home/pp/bin/caddy: No such file or directory > > $ file /home/pp/bin/caddy > /home/pp/bin/caddy: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), > dynamically linked, interpreter /lib/a

Re: No such file..?

On Thu, May 4, 2017 at 10:57 PM, Peter Passchier wrote: [...] > $ file /home/pp/bin/caddy > /home/pp/bin/caddy: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), > dynamically linked, interpreter /lib/amd64/ld.so.1, not stripped (I'm assuming you're trying to run this in a Linux system) Can y

Re: No such file..?

On 5/4/17 11:57 PM, Peter Passchier wrote: > I downloaded a Solaris binary and I was wondering whether I could get it > to execute with the --version commandline argument (it worked for an > arm7 binary before). But that's not what concerns me. > > $ /home/pp/bin/caddy --version > -bash: /home/pp/

No such file..?

I downloaded a Solaris binary and I was wondering whether I could get it to execute with the --version commandline argument (it worked for an arm7 binary before). But that's not what concerns me. $ /home/pp/bin/caddy --version -bash: /home/pp/bin/caddy: No such file or directory $ file /home/pp/b