Date: Sat, 2 Feb 2013 12:08:02 +0100 From: Baptiste Daroussin <bapt@freebsd.org> To: Eitan Adler <lists@eitanadler.com> Cc: FreeBSD Ports <ports@freebsd.org> Subject: Re: zsh crash Message-ID: <20130202110802.GO6282@ithaqua.etoilebsd.net> In-Reply-To: <CAF6rxgnAcrej8BbmhPKVD3Bippet-K8D0GVKcZKGwbhwXNwHeg@mail.gmail.com> References: <CAF6rxgnAcrej8BbmhPKVD3Bippet-K8D0GVKcZKGwbhwXNwHeg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Vy1A5eXR7jld12ZH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 01, 2013 at 11:33:55PM -0500, Eitan Adler wrote: > Hi all, >=20 > I am seeing a very common crash now in zsh. The backtrace is here > (and this it shows a corrupt stack / missing symbols). > I'm still working on figuring out a reproducible version of the crash, > but so far it seems to relate to sending SIGINT. >=20 Without anyway to reproduce, this is pretty useless to me. I'm aware of at = least 2 ways of crashing zsh, which I haven't patched yet because they are quite uncommon use, but nothing close to what you say, I'd be very interested in = a way to reproduce. regards, Bapt --Vy1A5eXR7jld12ZH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEM85IACgkQ8kTtMUmk6ExzgACfXcHMPnThWKHz1clxuT7+U8p4 /cIAoK5XPkBwSfPmJXYXGm7du6zlwUXz =Ql4c -----END PGP SIGNATURE----- --Vy1A5eXR7jld12ZH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130202110802.GO6282>