Re: Complex config triggering Segfault in pattern matching code.

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Dec 14,  6:20pm, Peter Stephenson wrote:
}
} Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
} > #280 recursiveedit (args=0x7fb1f7f4ba70) at zle_main.c:181
} > 
} > So at this point we haven't even finished initializing ZLE yet, but one of
} > these "auto-fu" functions has recursively invoked it.  This is a recipe for 
} > disaster if ever I saw one.
} 
} After zle-line-init runs (in zleread),the next thing we do is zrefresh()
} and then zlecore().  So I think it *has* finished initialising ---
} zrefresh() and zlecore() are the stuff that we can only do when zsh is
} set up and we can do them at this point.

OK; that is after all why I invoked you ... (turn three times counter-
clockwise, then fling salt over your right shoulder and ...)

} > #126 completecall (args=0x7fb1f7f38918) at zle_tricky.c:208
} 
} This is utterly bizarre, but, again, I'm not really sure what the core
} shell should be disallowing.  It's up to the user rather than the shell
} not to complete anything before they've even started up the command
} line...

After thinking about this, it occurred to me that we're inside recursive-
edit, so probably the stack has grown and shrunk several times as input
was typed before we got the trace that led to this particular error.  So
the buffer likely wasn't empty after all.