Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

This is an annoying bug related to ZSH and python virtualenvwrapper. I couldn't find any clue on this anywhere on the web, so I am going to make a new post in SU!

Symptoms

  1. Use ZSH, and python virtualenvwrapper is installed (so that workon command works)
  2. Type into the shell, % workon <TAB> to trigger tab-completion of available virtual environments.
  3. Then, ZSH crashes and the current shell is closed unexpectedly.

Why does this happen? Who is the culprit, zsh or virtualenvwrapper?

Diagnostics

AFAIK, zsh is suspicious, since we can find segmentation fault log messages.

Segfault happend at: 0x452005 <popheap+85>: mov 0x18(%r12),%rdi PC(0x00452005) ok

Sometimes (but hardly) works well, but almost always it is reproducible for several machines. I am now going to inspect on this, for various environments, for zsh versions, or for other configurations.

Environments in which I've experienced:

  • Linux Ubuntu 12.04.02 LTS (Kernel: Linux 3.2.0-54-generic x86_64)
  • ZSH: zsh 4.3.17-1ubuntu1

  • UPD1 : Reproducible also in the latest ZSH, 5.0.2 (configured and compiled from the source)

References

Thanks.

share|improve this question
    
Can you try to use a current, official zsh version? –  mpy Oct 16 '13 at 7:37
    
Same for other zsh versions (including 5.0.2), too. (UPD1) –  Jongwook Choi Oct 17 '13 at 4:08
    
This bug (together with another one) was discussed on the zsh-workers mailing list back in may: zsh.org/mla/workers//2013/msg00442.html It seems, that the devs still need input from s/b who can reproduce the issue. –  mpy Oct 17 '13 at 8:36

1 Answer 1

Seems like the problem is with ZSH plugin 'virtualenvwrapper' on systems with a particular virtualenvwrapper environment. For instannce; I installed manually rather than using 'pip install virtualenvwrapper.'

Removing `virtualenvwrapper' from my .zshrc seemed to work–around the issue. I would bet that reinstalling virtualenvwrapper using pip will fix the issue in many cases.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.