From: Bart Schaefer <schaefer@brasslantern.com>
To: Chi-Hsuan Yen <yan12125@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] SIGSEGV under certain circumstances
Date: Sat, 4 Mar 2017 15:11:37 -0800 [thread overview]
Message-ID: <170304151137.ZM30694@torch.brasslantern.com> (raw)
In-Reply-To: <CAMNjDR1CUaw2AXbEDLP94R=4VCNj1yc=d3OcVj=tO6FZXAEqPQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2017-03-04 23:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:38 Chi-Hsuan Yen
2017-03-04 23:11 ` Bart Schaefer [this message]
2017-03-05 12:55 ` Chi-Hsuan Yen
2017-03-05 13:09 ` Chi-Hsuan Yen
2017-03-05 16:00 ` Bart Schaefer
2017-03-05 16:17 ` Peter Stephenson
2017-03-05 18:42 ` Bart Schaefer
2017-03-05 18:52 ` Peter Stephenson
2017-03-05 21:45 ` Bart Schaefer
2017-03-05 22:31 ` Bart Schaefer
2017-03-05 22:41 ` Daniel Shahaf
2017-03-05 22:51 ` Bart Schaefer
2017-03-05 23:07 ` Bart Schaefer
2017-03-06 0:23 ` Bart Schaefer
2017-03-06 9:47 ` Peter Stephenson
2017-03-06 17:10 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170304151137.ZM30694@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=yan12125@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).