zsh-workers
 help / color / mirror / code / Atom feed
* Zsh - possible bug report
@ 2017-09-10 13:00 Simon Guilliams
  2017-09-10 16:50 ` Peter Stephenson
  0 siblings, 1 reply; 2+ messages in thread
From: Simon Guilliams @ 2017-09-10 13:00 UTC (permalink / raw)
  To: zsh-workers

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

Hello,

I have found a behavior of zsh I cannot explain. I don't know if it is a
bug and I hope this is not a duplicate.

$ cat print-argv0.c
> #include <stdio.h>
> int main(int ac, char **av)
> {
> if (ac > 0)
> fputs(av[0], stdout);
> }
> $ cc print-argv0.c
> $ zsh -f -c "exec -a '' ./a.out | hexdump -vC"
> 00000000  9b 9b                                             |..|
> 00000002
> $ zsh -f -c "exec -a \"\" ./a.out | hexdump -vC"
> 00000000  9c 9c                                             |..|
> 00000002


Zsh makes argv[0] hold two bytes, 0x9b9b or 0x9c9c depending on quotes or
double-quotes.
Bash does make argv[0] an empty string.

$ bash -c "exec -a '' ./a.out | hexdump -vC"
> $ bash -c "exec -a \"\" ./a.out | hexdump -vC"
> $


Why does this happen? Is this expected behavior?

Thank you

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Zsh - possible bug report
  2017-09-10 13:00 Zsh - possible bug report Simon Guilliams
@ 2017-09-10 16:50 ` Peter Stephenson
  0 siblings, 0 replies; 2+ messages in thread
From: Peter Stephenson @ 2017-09-10 16:50 UTC (permalink / raw)
  To: Simon Guilliams, zsh-workers

On Sun, 10 Sep 2017 15:00:28 +0200
Simon Guilliams <simon.guilliams@gmail.com> wrote:
> Hello,
> 
> I have found a behavior of zsh I cannot explain. I don't know if it is a
> bug and I hope this is not a duplicate.
> 
> $ cat print-argv0.c
> > #include <stdio.h>
> > int main(int ac, char **av)
> > {
> > if (ac > 0)
> > fputs(av[0], stdout);
> > }
> > $ cc print-argv0.c
> > $ zsh -f -c "exec -a '' ./a.out | hexdump -vC"
> > 00000000  9b 9b                                             |..|
> > 00000002
> > $ zsh -f -c "exec -a \"\" ./a.out | hexdump -vC"
> > 00000000  9c 9c                                             |..|
> > 00000002

Bug.

Thanks for the clear demonstration.

pws

diff --git a/Src/exec.c b/Src/exec.c
index 76a6bb1..e2432fd 100644
--- a/Src/exec.c
+++ b/Src/exec.c
@@ -3007,6 +3007,9 @@ execcmd_exec(Estate state, Execcmd_params eparams,
 		}
 		if (exec_argv0) {
 		    char *str, *s;
+		    exec_argv0 = dupstring(exec_argv0);
+		    remnulargs(exec_argv0);
+		    untokenize(exec_argv0);
 		    size_t sz = strlen(exec_argv0);
 		    str = s = zalloc(5 + 1 + sz + 1);
 		    strcpy(s, "ARGV0=");
diff --git a/Test/A01grammar.ztst b/Test/A01grammar.ztst
index 0302c96..5e7d6ac 100644
--- a/Test/A01grammar.ztst
+++ b/Test/A01grammar.ztst
@@ -103,6 +103,12 @@
 0:`exec' with -a option, no space
 >/bin/SPLOOSH
 
+  (exec -a foo* $ZTST_testdir/../Src/zsh -fc 'print -r -- ${(V)0}')
+  (exec -a "" $ZTST_testdir/../Src/zsh -fc 'print -r -- ${(V)0}')
+0:rationalisation of arguments to exec -a
+>foo*
+>
+
   (
     opts=(-a /bin/WHOOOSH)
     exec $opts /bin/sh -c 'echo $0'


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-09-10 16:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-10 13:00 Zsh - possible bug report Simon Guilliams
2017-09-10 16:50 ` Peter Stephenson

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).