From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24458 invoked by alias); 5 Mar 2017 13:09:46 -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: 40735 Received: (qmail 12258 invoked from network); 5 Mar 2017 13:09:46 -0000 X-Qmail-Scanner-Diagnostics: from park01.gkg.net 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(205.235.26.22):SA:0(0.8/5.0):. Processed in 1.903853 secs); 05 Mar 2017 13:09:46 -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.8 required=5.0 tests=FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_SORBS_SPAM, RP_MATCHES_RCVD,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: SRS0=KWNb=2O=gmail.com=yan12125@bounces.park01.gkg.net X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at bounces.park01.gkg.net does not designate permitted sender hosts) X-Virus-Scanned: by amavisd-new at gkg.net Authentication-Results: amavisd4.gkg.net (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 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=MC9fR2J7QPI9J32LMilphgTs+9QbRKgr+OD9X62/niQ=; b=Ng7zmtl85Khk7nJBWhj5giEmIwJj6UFvjwuG4D/JwL52/xOfqKRXLlEQNxpmgszqCy 8F9oNEM+pNJSgWNKHMtJ4R6YnyZmAxU6owAs3b6iVARFjTe7ao8TWkqeS6Mk2jWeJ6e2 i4tubLqjMeBPVLCvsdeZRMMTBuaYMe7S1q/xmV55ioi5KlKgH96f5u89ebd6GaZUPBGM KEXSAIxrJ525JMvPTZrq0rg/wbL/SkdyNibzFb9qitWwvRfpGNDoFoQD1NRga35MFYht OMk+xgKjy74XOhdiiB0i8MOyj8bkD0L1RurPUfR64hflhMp5h+bVwulmasHjKiAlLQzC Gq7g== 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=MC9fR2J7QPI9J32LMilphgTs+9QbRKgr+OD9X62/niQ=; b=bOTkQtOcIfzqiC+IOAMWvTnuneVPfybKkbUCroj9n1hlhY6FfcCY/bIBGT7YoHVG/+ JO2XrDq1oKO+CQodDOPQLliCvlAYl05XMD5ynIHKmMuAZs8axuepvomO4crNOtHwaIrU Fl0+iNIimHd+tXNLIYOmK5wAqZhTyCycmXP7I6huduv/Fev7QNGSQKPYBkC0Ouusam2Q WHlw4sk6X3WM6lKEV8oUBp2G8L1I2Hb7G9Re1JqzZclC52h/toSyzhwxESKTER9oBj13 PewLhJZ61bd1xBoqY1vjP/KApGacMXaW44kSBkZBcIlLJ+LhWH2SR1ArpIA4NoyJBqAm cLUA== X-Gm-Message-State: AMke39nN7tMq8IvONCWyC0e90vboQCjV4GKRj6D4Tl2wr6G+oS4Z1mVo93ZNR3hFq2JrH4PdXdOdUAHAZn8T0w== X-Received: by 10.55.43.213 with SMTP id r82mr11863292qkr.196.1488719354651; Sun, 05 Mar 2017 05:09:14 -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 21:09:14 +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. (I forgot that gmail servers are blocked, so I re-post my logs) 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). [2] and [3] contains logs of vgdb, which I heard that can give more information than either valgrind or gdb. [1] https://gist.github.com/yan12125/014c7a7510d1d9bd9ac8edf142a0c65d#file-valgrind-log [2] https://gist.github.com/yan12125/014c7a7510d1d9bd9ac8edf142a0c65d#file-valgrind-log-with-vgdb [3] https://gist.github.com/yan12125/014c7a7510d1d9bd9ac8edf142a0c65d#file-gdb-backtrace-from-vgdb