From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17848 invoked by alias); 17 Jun 2015 15:23:28 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35507 Received: (qmail 28037 invoked from network); 17 Jun 2015 15:23:25 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=LSOCHUmqgab96mYQE11UIoJ5FfI/0rZhCGGeq3UnaQ4=; b=ItNeTJsSMweb39OD6kBsTV95kz/fK3N0QOgShK7nR8xHInZ9bPQmLnkOseIOj+BRDt 7ADv2oAhsef6lw7Y4F578OWHs9s5Z0VHud9ISKLxFUa3yQr3Gm3nJ2Qe57khf6KslwAw uCy5TAE1fT2r0LA4mYO5QRl3gK+TufCymN+s7fwhpngHKBRTKzqzQDwSoKMlzSIO0zJy CTCNODRBlz5SlA4J0Z7N7cZZ1Tf06J3I5MYXCeif36VQuJGyJAIKKfscXt8AlEypwBlm 51uQCpK1MKBWV9H/YxecfSxXvsV6Ad5UbDPUmg0JY8I9rxijBuEdGRL70BEt4lQxXyyR yFxA== X-Gm-Message-State: ALoCoQmvkXalrk1V3QJc5YfCZEAG09SsODe5yPBzUIS0BKDHYATAckE42qVr3i6IYDNh1MbVvKFR X-Received: by 10.202.239.138 with SMTP id n132mr4679344oih.99.1434554604217; Wed, 17 Jun 2015 08:23:24 -0700 (PDT) From: Bart Schaefer Message-Id: <150617082305.ZM907@torch.brasslantern.com> Date: Wed, 17 Jun 2015 08:23:05 -0700 In-Reply-To: <20150617061628.GA27402@localhost.localdomain> Comments: In reply to Han Pingtian "[PATCH] don't let char class disturb end finding" (Jun 17, 2:16pm) References: <20150617061628.GA27402@localhost.localdomain> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: [PATCH] don't let char class disturb end finding MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 17, 2:16pm, Han Pingtian wrote: } } This patch try to fix this problem: } } compadd -M '[[:lower:]123456]=...' will cause the end of class to be the } ']' before 1 and will alloc range of memory less than enough for the } cpattern. I don't see anything obviously wrong with the patch, but when I try the above example directly I get "unknown match specification character `['" both before and after applying your patch (and no complaints of memory misuse from valgrind, even before your patch). Is that the correct example to reproduce the error? I also tried '[[:lower:]123456]=[[:upper:]abcdef]' with the same result.