Zsh Mailing List Archive
Messages sorted by:
Re: [BUG] SIGSEGV under certain circumstances
- X-seq: zsh-workers 40735
- From: Chi-Hsuan Yen <yan12125@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: [BUG] SIGSEGV under certain circumstances
- Date: Sun, 5 Mar 2017 21:09:14 +0800
- Authentication-results: amavisd4.gkg.net (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- 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==
- In-reply-to: <170304151137.ZM30694@torch.brasslantern.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAMNjDR1CUaw2AXbEDLP94R=4VCNj1yc=d3OcVj=tO6FZXAEqPQ@mail.gmail.com> <170304151137.ZM30694@torch.brasslantern.com>
On 5 March 2017 at 07:11, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> 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 . (The GDB backtrace is also updated to the
new build for consistency).  and  contains logs of vgdb, which I
heard that can give more information than either valgrind or gdb.
Messages sorted by: