zsh-workers
 help / color / mirror / code / Atom feed
From: Nicholas Riley <njriley@illinois.edu>
To: zsh-workers@zsh.org
Subject: Re: compctl crash
Date: Thu, 18 Apr 2013 18:09:38 -0500	[thread overview]
Message-ID: <njriley-B1E1AB.18093818042013@news.gmane.org> (raw)
In-Reply-To: <87obdb786z.fsf@ft.bewatermyfriend.org>

In article <87obdb786z.fsf@ft.bewatermyfriend.org>,
 Frank Terbeck <ft@bewatermyfriend.org> wrote:

> I tried 4.3.10 and a git build that's a few days old, but I could not
> reproduce the problem.

Sorry, given I tried it on two different OSes and wildly differing 
versions I assumed it would be trivial to reproduce.

> > I had thought it would reset all the compctl-defined completions.
> 
> Note, that compctl is the older of the two completion systems, that zsh
> implements. The newer - compsys - is the one almost everybody uses
> (unless they still get that trusty old i386SX-16 another go every once
> in a while...).

Yeah, the only reason I'm even bothering is in my other email - because 
virtualenvwrapper uses it.

> > glibc logs something of the form:
> >
> > *** glibc detected *** zsh: double free or corruption (!prev): 
> > 0x09b89ca8 ***
> 
> Do you get a coredump? If so, could you load it into gdb and get a
> backtrace?

Program received signal SIGABRT, Aborted.
0xf57fe416 in __kernel_vsyscall ()
(gdb) bt
#0  0xf57fe416 in __kernel_vsyscall ()
#1  0xb7e45781 in raise () from /lib/i686/cmov/libc.so.6
#2  0xb7e48bb2 in abort () from /lib/i686/cmov/libc.so.6
#3  0xb7e7be75 in ?? () from /lib/i686/cmov/libc.so.6
#4  0xb7e85f71 in ?? () from /lib/i686/cmov/libc.so.6
#5  0xb7e877c8 in ?? () from /lib/i686/cmov/libc.so.6
#6  0xb7e8a8ad in free () from /lib/i686/cmov/libc.so.6
#7  0x080999a5 in zfree (p=0x8108240, sz=92) at mem.c:1719
#8  0xb7ba7666 in freecompctl (cc=0x8108240) at compctl.c:141
#9  0xb7baad43 in bin_compctl (name=0xb7c166f8 "compctl", 
argv=0xbffff294, 
    ops=0xbffff2d4, func=0) at compctl.c:1591
#10 0x08055b16 in execbuiltin (args=0xb7c166d0, bn=0xb7bb3524) at 
builtin.c:450
#11 0x080701c7 in execcmd (state=0xbffff940, input=0, output=0, how=18, 
    last1=2) at exec.c:3266
#12 0x0806bc74 in execpline2 (state=0xbffff940, pcode=131, how=18, 
input=0, 
    output=0, last1=0) at exec.c:1677
#13 0x0806b0c6 in execpline (state=0xbffff940, slcode=4098, how=18, 
last1=0)
    at exec.c:1462
#14 0x0806a908 in execlist (state=0xbffff940, dont_change_job=0, 
exiting=0)
    at exec.c:1245
#15 0x0806a388 in execode (p=0xb7c16648, dont_change_job=0, exiting=0, 
    context=0x80da3f7 "toplevel") at exec.c:1057
#16 0x08084c8c in loop (toplevel=1, justonce=0) at init.c:185
#17 0x08087d44 in zsh_main (argc=2, argv=0xbffffaa4) at init.c:1617
#18 0x0805512f in main (argc=2, argv=0xbffffaa4) at ./main.c:93
-- 
Nicholas Riley <njriley@illinois.edu>


  reply	other threads:[~2013-04-18 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 22:01 Nicholas Riley
2013-04-18 23:03 ` Frank Terbeck
2013-04-18 23:09   ` Nicholas Riley [this message]
2013-04-18 23:59 ` Bart Schaefer
2013-04-20 19:44   ` Nicholas Riley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=njriley-B1E1AB.18093818042013@news.gmane.org \
    --to=njriley@illinois.edu \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).