From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13906 invoked by alias); 6 Mar 2017 18:31:25 -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: 40770 Received: (qmail 13822 invoked from network); 6 Mar 2017 18:31:25 -0000 X-Qmail-Scanner-Diagnostics: from mail-qk0-f179.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.220.179):SA:0(0.5/5.0):. Processed in 0.859471 secs); 06 Mar 2017 18:31:25 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.5 required=5.0 tests=DATE_IN_PAST_24_48, FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_SPAM,SPF_PASS,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: yan12125@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.220.179 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lDszBQNMwTpLvu6qjw+//X47z7vmeys+gSvKgH1NGWc=; b=iXTPKU1xVoWydSpqyXz0hRvAM54Rm31VSoN1O5lNGHP7EI227+UNi0YuqISjjdBnPY /lEN06U2GZhFPL4EDg1qQkwcSa37Pzbw54e5SET/pERodOp7pEIkvupTO2h/zEfAvZtb g6z1VpfRQ3U5KkUcc3ZvP3Vgz1B9yR6oNwCawe6RRcBxGFXR9pBXNigRl5KR40b3MfYb q2UwqbLnoyfl5Il78GTHYX3VfQErK4rMihWtH2eu1KFPe6Efq7syliLil5KaHA+wT+nJ QHwI/hHwDP9XjKftpwCsaL47xZ8rudFq4nptrauvgkl81rprbvEOJMQFGgCKC1BFCvZ6 XNKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lDszBQNMwTpLvu6qjw+//X47z7vmeys+gSvKgH1NGWc=; b=MIZwdAlUAsJ9rKFIN20jtqj71YsEmL4E5ZXpKOZi4AZt3sYmbg31gbtOtQ2eysMdTl XXkpgFdZPx6iQcqFm57SteMe0VQV60QjURODn5i8imh9KnysFodz2CWXbRnNn1To03nm 7+e6of1pfdivLwzMnewJ2Xx8uiaUjvriQxOqYcLWcwNqW54JGcmvohepv6Xr2NF73zfP 9+EzZsoYluOZ5lRk4sknaLEdgWmLAYD4uzo3VfkRJveNZ7IeYXPSco1NDA7hKBMpj9zQ F0NDT90uzmP+fD7yqNJ5BJXBzNyhCv9e5sd7qvzgj6oi90h6AUoT1mz9E6WAddgdWNWT ygNQ== X-Gm-Message-State: AMke39nAIwPL/LwtcB4KJHeULeLKFPy3hCtfBrLG1+yOB/EgaM8mzgqYCAjELOYTAqlXpEu3rcqocOWOE9bddg== X-Received: by 10.237.36.153 with SMTP id t25mr11904732qtc.134.1488718518575; Sun, 05 Mar 2017 04:55:18 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <170304151137.ZM30694@torch.brasslantern.com> References: <170304151137.ZM30694@torch.brasslantern.com> From: Chi-Hsuan Yen Date: Sun, 5 Mar 2017 20:55:18 +0800 Message-ID: Subject: Re: [BUG] SIGSEGV under certain circumstances To: Bart Schaefer Cc: Zsh hackers list Content-Type: text/plain; charset=UTF-8 On 5 March 2017 at 07:11, Bart Schaefer wrote: > On Mar 1, 11:38pm, Chi-Hsuan Yen wrote: > } > } My zsh version is d00931de5c2b7aa846daf137865dd05ac8d4be8a. > } > } By the way, after those steps ~/.zsh_history seems corrupted: > > I'm not sure the history is actually corrupted, because the history > file is stored with metafied characters which means you can't easily > examine it independently of reading it into zsh. There was a small > C program posted here some months ago that would unmetafy the file. > > However based on your steps to reproduce there likely is a problem > related to reading the history file back in again. > > The stack trace you provided is not helpful because it reveals the > point at which the corrupted memory is accessed but not the point > at which it became corrupted. A pass through valgrind might give > better information. Thanks for the tip. I re-compiled with commit 8522e996ecc88697344dcc4814367ec7e32e7deb and run zsh under valgrind. The log can be found in [1]. (The GDB backtrace is also updated to the new build for consistency). [1] https://gist.github.com/yan12125/014c7a7510d1d9bd9ac8edf142a0c65d#file-valgrind-log