{"thread":{"id":"33155","subject":"ZSH segmentation fault while completing \"git mv dir/\"","startedAt":"2013-03-11T12:30:41Z","lastAt":"2013-04-03T08:52:51Z","messageCount":12,"participants":["Matthieu Moy","Manlio Perillo","Jeff Epler","Felipe Contreras","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"211041","messageId":"vpqd2v686fi.fsf@grenoble-inp.fr","threadId":"33155","inReplyTo":null,"subject":"ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-03-11T12:30:41Z","receivedAt":"2013-03-11T12:30:41Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Hi,\n\nSince the recent update to bash completion, I often get a segmentation\nfault from ZSH. This is most likely a bug in ZSH, but it would be cool\nto avoid triggering it from Git.\n\nSteps to reproduce:\n\nmoy@anie:/tmp$$ git init zsh\nInitialized empty Git repository in /tmp/zsh/.git/\nmoy@anie:/tmp$$ cd zsh/\nmoy@anie:/tmp/zsh$$ mkdir foo\nmoy@anie:/tmp/zsh$$ touch foo/bar.txt\nmoy@anie:/tmp/zsh$$ git mv foo/zsh: segmentation fault  zsh\nmoy@anie:~$ zsh --version\nzsh 4.3.10 (i686-pc-linux-gnu)\n\n(this is ZSH packaged with Debian stable)\n\nAny ZSH guru to look into it?\n\nThanks,\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"211047","messageId":"513DF4D1.6000500@gmail.com","threadId":"33155","inReplyTo":"vpqd2v686fi.fsf@grenoble-inp.fr","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Manlio Perillo","fromEmail":"manlio.perillo@gmail.com","sentAt":"2013-03-11T15:14:25Z","receivedAt":"2013-03-11T15:14:25Z","isPatch":false,"sender":{"key":"manlio.perillo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6217088?v=4"},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nIl 11/03/2013 13:30, Matthieu Moy ha scritto:\n> Hi,\n> \n> Since the recent update to bash completion, I often get a segmentation\n> fault from ZSH. This is most likely a bug in ZSH, but it would be cool\n> to avoid triggering it from Git.\n> \n> [...]\n> moy@anie:~$ zsh --version\n> zsh 4.3.10 (i686-pc-linux-gnu)\n> \n> (this is ZSH packaged with Debian stable)\n> \n\nI have the same system, but I can't reproduce the problem.\nWhat is the content of your .zshrc file?\n\n\nRegards  Manlio Perillo\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.10 (GNU/Linux)\nComment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/\n\niEYEARECAAYFAlE99NAACgkQscQJ24LbaURIwgCbB9HmepRfvTqN2vh6H5/Ew7Mw\nWQMAn3CSiFViQ7j62fuBVKg6WJK+Yg/0\n=j4FV\n-----END PGP SIGNATURE-----\n"},{"id":"211048","messageId":"vpq8v5uueug.fsf@grenoble-inp.fr","threadId":"33155","inReplyTo":"513DF4D1.6000500@gmail.com","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-03-11T15:37:59Z","receivedAt":"2013-03-11T15:37:59Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Manlio Perillo <manlio.perillo@gmail.com> writes:\n\n> I have the same system, but I can't reproduce the problem.\n> What is the content of your .zshrc file?\n\nI could reproduce with ~/.zshrc containing just:\n\n----------------------------------------------\nfpath=(${HOME}/usr/etc/zsh ${fpath})\n\nautoload -Uz compinit\ncompinit\n\neval \"`dircolors`\"\nzstyle ':completion:*' list-colors ${(s.:.)LS_COLORS}\n----------------------------------------------\n\n${HOME}/usr/etc/zsh contains two links _git and git-completion.bash\npointing to Git's completion scripts in contrib/.\n\nRemoving any line aboves removes the segmentation fault.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"211071","messageId":"513E3190.20100@gmail.com","threadId":"33155","inReplyTo":"vpq8v5uueug.fsf@grenoble-inp.fr","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Manlio Perillo","fromEmail":"manlio.perillo@gmail.com","sentAt":"2013-03-11T19:33:36Z","receivedAt":"2013-03-11T19:33:36Z","isPatch":false,"sender":{"key":"manlio.perillo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6217088?v=4"},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nIl 11/03/2013 16:37, Matthieu Moy ha scritto:\n> [...]\n> I could reproduce with ~/.zshrc containing just:\n> \n> ----------------------------------------------\n> fpath=(${HOME}/usr/etc/zsh ${fpath})\n> \n> autoload -Uz compinit\n> compinit\n> \n> eval \"`dircolors`\"\n> zstyle ':completion:*' list-colors ${(s.:.)LS_COLORS}\n> ----------------------------------------------\n> \n> ${HOME}/usr/etc/zsh contains two links _git and git-completion.bash\n> pointing to Git's completion scripts in contrib/.\n> \n\nUsing this configuration I still can't reproduce the problem, using\ngit v1.8.2-rc3-8-g0c91a6f.\n\nBut I'm not a zsh expert.\n\n\n\nRegards   Manlio Perillo\n\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.10 (GNU/Linux)\nComment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/\n\niEYEARECAAYFAlE+MZAACgkQscQJ24LbaUSTuACfYmZV9cvroPzBUdJspw9abh24\nfk8AnRTjvCEJ3m8Y2m/5jCIVVNsJAcG7\n=5p6c\n-----END PGP SIGNATURE-----\n"},{"id":"211101","messageId":"20130312013736.GB7105@unpythonic.net","threadId":"33155","inReplyTo":"513E3190.20100@gmail.com","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Jeff Epler","fromEmail":"jepler@unpythonic.net","sentAt":"2013-03-12T01:37:36Z","receivedAt":"2013-03-12T01:37:36Z","isPatch":false,"sender":{"key":"jepler@unpythonic.net","avatar":"https://avatars.githubusercontent.com/u/1517291?v=4"},"body":"If it's dependent on eval \"`dircolors`\", it suggests it might be\ndependent on the size of the environment.  Maybe try with FOO=`perl -e\n'print \"x\"x1000'` for various values of 1000...\n\nJeff\n"},{"id":"211103","messageId":"vpqwqtdkq9z.fsf@grenoble-inp.fr","threadId":"33155","inReplyTo":"20130312013736.GB7105@unpythonic.net","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-03-12T07:53:28Z","receivedAt":"2013-03-12T07:53:28Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Jeff Epler <jepler@unpythonic.net> writes:\n\n> If it's dependent on eval \"`dircolors`\", it suggests it might be\n> dependent on the size of the environment.  Maybe try with FOO=`perl -e\n> 'print \"x\"x1000'` for various values of 1000...\n\nIt's not this, but I could reduce the problem to a slightly simpler\n.zshrc:\n\n-----------------------------------------------------------------\nfpath=(${HOME}/usr/etc/zsh ${fpath})\n\nautoload -Uz compinit\ncompinit\n\nzstyle ':completion:*' list-colors 'rs=0' 'di=01;34' 'ln=01;36' \\\n 'mh=00' 'pi=40;33' 'so=01;35' 'do=01;35' 'bd=40;33;01' 'cd=40;33;01' \\\n 'or=40;31;01' 'su=37;41' 'sg=30;43' 'ca=30;41' 'tw=30;42' 'ow=34;42' \\\n 'st=37;44' 'ex=01;32' '*.tar=01;31' '*.tgz=01;31' '*.arj=01;31'  \\\n '*.taz=01;31' '*.lzh=01;31' '*.lzma=01;31' '*.tlz=01;31' '*.txz=01;31' \\\n '*.zip=01;31' '*.z=01;31' '*.Z=01;31' '*.dz=01;31' '*.gz=01;31'  \\\n '*.lz=01;31' '*.xz=01;31' '*.bz2=01;31' '*.bz=01;31' '*.tbz=01;31'  \\\n '*.tbz2=01;31' '*.tz=01;31' '*.deb=01;31' '*.rpm=01;31' '*.jar=01;31' \\\n '*.rar=01;31' '*.ace=01;31' '*.pgm=01;35' '*.ppm=01;35'  \\\n '*.tga=01;35' '*.xbm=01;35' '*.zoo=01;31' '*.cpio=01;31' '*.7z=01;31' \\\n '*.rz=01;31' '*.jpg=01;35' '*.jpeg=01;35' '*.gif=01;35' \\\n '*.bmp=01;35' '*.pbm=01;35'\n-----------------------------------------------------------------\n\nThe problem disapears if I remove one of the arguments after list-colors\n(I didn't try with each of them, but picking 5 of them randomly and\nremoving it worked), so it seems to be a matter of number of arguments.\n\nOn git-completion.bash's side, it's really strange. If I comment out the\n\"case\" statement in _git_mv like this, the problem disapears:\n\n\n_git_mv ()\n{\n\t# case \"$cur\" in\n\t# --*)\n\t# \t__gitcomp \"--dry-run\"\n\t# \treturn\n\t# \t;;\n\t# esac\n\n\tif [ $(__git_count_arguments \"mv\") -gt 0 ]; then\n\t\t# We need to show both cached and untracked files (including\n\t\t# empty directories) since this may not be the last argument.\n\t\t__git_complete_index_file \"--cached --others --directory\"\n\telse\n\t\t__git_complete_index_file \"--cached\"\n\tfi\n}\n\nIf I add a simple 'echo \"$cur\" >&2' instead of the case, the problem\nreappears. Somehow, the fact that I'm accessing $cur seems to create the\nsegfault. Actually, the minimalistic _git_mv reproducing the problem is:\n\n_git_mv ()\n{\n\techo \"$cur\"\n\t[ $(__git_count_arguments \"mv\") = 1 ]\n\t__git_complete_index_file \"--cached --others --directory\"\n}\n\ngdb doesn't say much interesting since my ZSH isn't compile with debug:\n\n(gdb) r\nStarting program: /usr/bin/zsh \nanie$ cd /tmp/git\nanie$ git mv subdir/\nProgram received signal SIGSEGV, Segmentation fault.\n__strlen_sse2 () at ../sysdeps/i386/i686/multiarch/strlen.S:87\n87\t../sysdeps/i386/i686/multiarch/strlen.S: No such file or directory.\n\tin ../sysdeps/i386/i686/multiarch/strlen.S\nCurrent language:  auto\nThe current source language is \"auto; currently asm\".\n(gdb) where\n#0  __strlen_sse2 () at ../sysdeps/i386/i686/multiarch/strlen.S:87\n#1  0x080ae31d in ztrdup ()\n#2  0xb7b9d287 in permmatches () from /usr/lib/zsh/4.3.10/zsh/complete.so\n#3  0xb7b9a22e in ?? () from /usr/lib/zsh/4.3.10/zsh/complete.so\n#4  0x08098f33 in getstrvalue ()\n#5  0x08099e9d in ?? ()\n#6  0x0809acd7 in getindex ()\n#7  0x0809b3d9 in fetchvalue ()\n#8  0x080b0f84 in ?? ()\n#9  0x080b49a7 in prefork ()\n#10 0x08066cb9 in ?? ()\n#11 0x08067151 in ?? ()\n#12 0x0806cfc0 in execlist ()\n#13 0x0808984c in execif ()\n#14 0x080670c6 in ?? ()\n#15 0x0806cfc0 in execlist ()\n#16 0x0806d69a in execode ()\n#17 0x0806d785 in runshfunc ()\n#18 0xb7b99a7a in ?? () from /usr/lib/zsh/4.3.10/zsh/complete.so\n#19 0x0806d724 in runshfunc ()\n#20 0x0806db92 in doshfunc ()\n#21 0xb7ba3363 in ?? () from /usr/lib/zsh/4.3.10/zsh/complete.so\n#22 0xb7ba44dc in do_completion () from /usr/lib/zsh/4.3.10/zsh/complete.so\n#23 0xb7bdaf47 in ?? () from /usr/lib/zsh/4.3.10/zsh/zle.so\n#24 0xb7bd5b40 in completecall () from /usr/lib/zsh/4.3.10/zsh/zle.so\n#25 0xb7bc6f6e in execzlefunc () from /usr/lib/zsh/4.3.10/zsh/zle.so\n#26 0xb7bc72a2 in zlecore () from /usr/lib/zsh/4.3.10/zsh/zle.so\n#27 0xb7bc78d5 in zleread () from /usr/lib/zsh/4.3.10/zsh/zle.so\n#28 0xb7bc96ff in ?? () from /usr/lib/zsh/4.3.10/zsh/zle.so\n#29 0x0807d462 in zleentry ()\n#30 0x08080a31 in ingetc ()\n#31 0x0807b03c in ?? ()\n#32 0x08087fb6 in zshlex ()\n#33 0x080a3b4a in parse_event ()\n#34 0x0807f2f1 in loop ()\n#35 0x080800c6 in zsh_main ()\n#36 0x08054cbb in main ()\n\nI can't reproduce the problem with the exact same config and a freshly\ncompiled ZSH (so it's no use reporting the issue to the ZSH developers).\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"212791","messageId":"CAMP44s3ocY7qpESHCDRdHJBsH1DV+k1Z5OwSqsWndMZd_s6oBQ@mail.gmail.com","threadId":"33155","inReplyTo":"vpqwqtdkq9z.fsf@grenoble-inp.fr","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2013-04-01T10:11:34Z","receivedAt":"2013-04-01T10:11:34Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Tue, Mar 12, 2013 at 1:53 AM, Matthieu Moy\n<Matthieu.Moy@grenoble-inp.fr> wrote:\n\n> If I add a simple 'echo \"$cur\" >&2' instead of the case, the problem\n> reappears. Somehow, the fact that I'm accessing $cur seems to create the\n> segfault. Actually, the minimalistic _git_mv reproducing the problem is:\n>\n> _git_mv ()\n> {\n>         echo \"$cur\"\n>         [ $(__git_count_arguments \"mv\") = 1 ]\n>         __git_complete_index_file \"--cached --others --directory\"\n> }\n\nI managed to reproduce the issue, and to me, this is enough:\n\n_git_mv ()\n{\n__gitcomp_file 'bar.txt' 'foo/'\n}\n\nAnd this is a workaround:\n\n--- a/contrib/completion/git-completion.zsh\n+++ b/contrib/completion/git-completion.zsh\n@@ -66,7 +66,7 @@ __gitcomp_file ()\n\n        local IFS=$'\\n'\n        compset -P '*[=:]'\n-       compadd -Q -p \"${2-}\" -f -- ${=1} && _ret=0\n+       compadd -Q -p \"${2-}\" -- ${=1} && _ret=0\n }\n\n _git ()\n\nCheers.\n\n--\nFelipe Contreras\n"},{"id":"212882","messageId":"vpqwqslgfzf.fsf@grenoble-inp.fr","threadId":"33155","inReplyTo":"CAMP44s3ocY7qpESHCDRdHJBsH1DV+k1Z5OwSqsWndMZd_s6oBQ@mail.gmail.com","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-04-02T14:32:52Z","receivedAt":"2013-04-02T14:32:52Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Felipe Contreras <felipe.contreras@gmail.com> writes:\n\n> And this is a workaround:\n>\n> --- a/contrib/completion/git-completion.zsh\n> +++ b/contrib/completion/git-completion.zsh\n> @@ -66,7 +66,7 @@ __gitcomp_file ()\n>\n>         local IFS=$'\\n'\n>         compset -P '*[=:]'\n> -       compadd -Q -p \"${2-}\" -f -- ${=1} && _ret=0\n> +       compadd -Q -p \"${2-}\" -- ${=1} && _ret=0\n>  }\n\nOK, not something we want to apply to git.git, but this means a\nworkaround for users is to create a _git file with this content instead\ninstead of copying/symlinking git-completion.zsh as _git (replace\n$GIT_ROOT_PATH with the appropriate value):\n\n. $GIT_ROOT_PATH/contrib/completion/git-completion.zsh\n\n# Work around ZSH bug on zsh 4.3.10-dev-1-cvs0720, which segfaults\n# when completing \"git mv subdir/<tab>\" by redefining __gitcomp_file\n__gitcomp_file ()\n{\n\temulate -L zsh\n\n\tlocal IFS=$'\\n'\n\tcompset -P '*[=:]'\n\t# The original had a -f here to indicate file completion.\n\tcompadd -Q -p \"${2-}\" -- ${=1} && _ret=0\n}\n\n(Hope this helps in case someone has the same problem and finds this\nthread ...)\n\nThanks,\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"212902","messageId":"7va9pgg9p7.fsf@alter.siamese.dyndns.org","threadId":"33155","inReplyTo":"vpqwqslgfzf.fsf@grenoble-inp.fr","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-04-02T16:48:36Z","receivedAt":"2013-04-02T16:48:36Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:\n\n> Felipe Contreras <felipe.contreras@gmail.com> writes:\n>\n>> And this is a workaround:\n>>\n>> --- a/contrib/completion/git-completion.zsh\n>> +++ b/contrib/completion/git-completion.zsh\n>> @@ -66,7 +66,7 @@ __gitcomp_file ()\n>>\n>>         local IFS=$'\\n'\n>>         compset -P '*[=:]'\n>> -       compadd -Q -p \"${2-}\" -f -- ${=1} && _ret=0\n>> +       compadd -Q -p \"${2-}\" -- ${=1} && _ret=0\n>>  }\n>\n> OK, not something we want to apply to git.git, but this means a\n> workaround for users is to ...\n\nWould it help users more to have that as part of the instruction at\nthe beginning of contrib/completion/git-completion.zsh where it\nalready says \"here is how you use it via fpath\", than leaving it\nhere in the list archive?\n\n> (Hope this helps in case someone has the same problem and finds this\n> thread ...)\n"},{"id":"212911","messageId":"vpqppyceuka.fsf@grenoble-inp.fr","threadId":"33155","inReplyTo":"7va9pgg9p7.fsf@alter.siamese.dyndns.org","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-04-02T17:00:53Z","receivedAt":"2013-04-02T17:00:53Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> Would it help users more to have that as part of the instruction at\n> the beginning of contrib/completion/git-completion.zsh where it\n> already says \"here is how you use it via fpath\", than leaving it\n> here in the list archive?\n\nJuging from the answers I got, I do not think many people are hit by the\nbug, and the problem will anyway disappear as people update their ZSH,\nso I'm not sure it's worth the trouble.\n\nThis thread is already #1 on google with \"git zsh segmentation fault\" so\nit's not terribly difficult to find.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"212991","messageId":"515B45AB.5030503@gmail.com","threadId":"33155","inReplyTo":"vpqwqslgfzf.fsf@grenoble-inp.fr","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Manlio Perillo","fromEmail":"manlio.perillo@gmail.com","sentAt":"2013-04-02T20:55:07Z","receivedAt":"2013-04-02T20:55:07Z","isPatch":false,"sender":{"key":"manlio.perillo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6217088?v=4"},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nIl 02/04/2013 16:32, Matthieu Moy ha scritto:\n> Felipe Contreras <felipe.contreras@gmail.com> writes:\n> \n>> And this is a workaround:\n>>\n>> --- a/contrib/completion/git-completion.zsh\n>> +++ b/contrib/completion/git-completion.zsh\n>> @@ -66,7 +66,7 @@ __gitcomp_file ()\n>>\n>>         local IFS=$'\\n'\n>>         compset -P '*[=:]'\n>> -       compadd -Q -p \"${2-}\" -f -- ${=1} && _ret=0\n>> +       compadd -Q -p \"${2-}\" -- ${=1} && _ret=0\n>>  }\n> \n> OK, not something we want to apply to git.git, but this means a\n> workaround for users is to create a _git file with this content instead\n> instead of copying/symlinking git-completion.zsh as _git (replace\n> $GIT_ROOT_PATH with the appropriate value)\n\nBy the way: have you filled a bug report to Debian?\n\n\nRegards  Manlio\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.10 (GNU/Linux)\nComment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/\n\niEYEARECAAYFAlFbRasACgkQscQJ24LbaUTDZQCfbfF5yhxCfUSaWdv0pE7++X3l\nLc0AniAw5lEL6iunM+Tw8HvYxGwjuYYh\n=KpQI\n-----END PGP SIGNATURE-----\n"},{"id":"213025","messageId":"vpq4nfoatcs.fsf@grenoble-inp.fr","threadId":"33155","inReplyTo":"515B45AB.5030503@gmail.com","subject":"Re: ZSH segmentation fault while completing \"git mv dir/\"","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-04-03T08:52:51Z","receivedAt":"2013-04-03T08:52:51Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Manlio Perillo <manlio.perillo@gmail.com> writes:\n\n> By the way: have you filled a bug report to Debian?\n\nNo, but this is a bug touching very few users, in Debian stable which is\nreaching its end of life. I do not think the Debian folks would be\ninterested in fixing this non-security, non-critical bug now.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"}]}