zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: John Ramsden <ramsdenj@riseup.net>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Bug - invalid pointer
Date: Fri, 13 Apr 2018 19:16:30 -0700	[thread overview]
Message-ID: <CAH+w=7b7N7RZFjnt1o8ZmyDHbW9pAZOg0XjnqKS9Vk=9AJ11ow@mail.gmail.com> (raw)
In-Reply-To: <1523671201.1300523.1337561832.23CF134B@webmail.messagingengine.com>

On Fri, Apr 13, 2018 at 7:00 PM, John Ramsden <ramsdenj@riseup.net> wrote:
> Okay, so I went ahead and recompiled by adding 'options=(debug !strip)' to my PKGBUILD on Arch. That's all I changed so if I need to do something else to get full debugging symbols let me know.

Well, there's what I said in other email about what gets passed to configure.

However, the trace you provided points to code for managing the width
of the window, so I would guess the window is changing size while zle
is trying to get started.  There's code to try to block SIGWINCH until
zle is actually ready to go, expecting the window to therefore have
stabilized by the time its size is needed, but it looks like this is
slipping around that somehow.


  reply	other threads:[~2018-04-14  2:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14  2:00 John Ramsden
2018-04-14  2:16 ` Bart Schaefer [this message]
2018-04-14  3:19   ` John Ramsden
2018-04-14  3:57     ` Bart Schaefer
2018-04-14  5:34       ` John Ramsden
2018-04-14 10:20         ` Julien Nicoulaud
2018-04-14 19:34           ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2018-04-13 21:56 John Ramsden
2018-04-14  1:29 ` Bart Schaefer
2018-04-14  1:43   ` John Ramsden
2018-04-14  1:57     ` 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='CAH+w=7b7N7RZFjnt1o8ZmyDHbW9pAZOg0XjnqKS9Vk=9AJ11ow@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=ramsdenj@riseup.net \
    --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).