zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Core dump doing accept-and-menu-complete in menu-selection
Date: Sat, 20 May 2000 17:34:31 +0000	[thread overview]
Message-ID: <1000520173431.ZM9577@candle.brasslantern.com> (raw)

This is with something close to the very latest patches ...

In the top zsh source directory:

zagzig[71] ls *<C-x e>

I now have a menu-selection with all-expansions first and then the individual
files below that, and finally the original string below that.  My styles put
the list of files in most-recently-modified order.

I typed TAB to move to the first file name (Completion), typed ^X TAB (which
I have bound to accept-and-menu-complete) to get to Config, typed TAB to move
on to Doc, typed ^X TAB again, and kaboom.

#0  0x401649fe in domenuselect (dummy=0x4013502c, dat=0xbffff3fc)
    at ../../../zsh-3.1.6/Src/Zle/complist.c:1804
1804                        if (*p == minfo.cur)

It looks as if `p' is garbage at this point, see below.

(gdb) where
#0  0x401649fe in domenuselect (dummy=0x4013502c, dat=0xbffff3fc)
    at ../../../zsh-3.1.6/Src/Zle/complist.c:1804
#1  0x8085694 in runhookdef (h=0x4013502c, d=0xbffff3fc)
    at ../../zsh-3.1.6/Src/module.c:1609
#2  0x4011fe6d in after_complete (dummy=0x40115bb0, dat=0xbffff488)
    at ../../../zsh-3.1.6/Src/Zle/compcore.c:507
#3  0x80856f6 in runhookdef (h=0x40115bb0, d=0xbffff488)
    at ../../zsh-3.1.6/Src/module.c:1615
#4  0x40105bf6 in docomplete (lst=0)
    at ../../../zsh-3.1.6/Src/Zle/zle_tricky.c:773
#5  0x40104577 in completeword (args=0x40115b04)
    at ../../../zsh-3.1.6/Src/Zle/zle_tricky.c:203
#6  0x40104461 in completecall (args=0x40115b04)
    at ../../../zsh-3.1.6/Src/Zle/zle_tricky.c:180
#7  0x400f9b33 in execzlefunc (func=0x80d9cb8, args=0x40115b04)
    at ../../../zsh-3.1.6/Src/Zle/zle_main.c:645
#8  0x400f959f in zleread (lp=0x80c4c68 "%m%(#.#.%1v)%h%(#.#.%2v) ", 
    rp=0x80d0068 "3.1.7-pre-3", flags=3)
    at ../../../zsh-3.1.6/Src/Zle/zle_main.c:564
#9  0x80737da in inputline () at ../../zsh-3.1.6/Src/input.c:265
#10 0x80736cd in ingetc () at ../../zsh-3.1.6/Src/input.c:210
#11 0x806cd6c in ihgetc () at ../../zsh-3.1.6/Src/hist.c:242
#12 0x80785a0 in gettok () at ../../zsh-3.1.6/Src/lex.c:621
#13 0x8077d41 in yylex () at ../../zsh-3.1.6/Src/lex.c:337
#14 0x808d918 in parse_event () at ../../zsh-3.1.6/Src/parse.c:421
#15 0x80710a3 in loop (toplevel=1, justonce=0)
    at ../../zsh-3.1.6/Src/init.c:121
#16 0x8050dc0 in main (argc=2, argv=0xbffff6bc)
    at ../../zsh-3.1.6/Src/main.c:86
(gdb) p p
$1 = (struct cmatch ***) 0x8101000
(gdb) 

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


                 reply	other threads:[~2000-05-20 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1000520173431.ZM9577@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).