zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: A repeating core, just sharing backtrace
Date: Thu, 5 Jul 2018 15:40:30 +0200	[thread overview]
Message-ID: <CAKc7PVBQn-ZjZ1T0TLqofETRiRw3xTExJ3aN10FWPqEQSi180w@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVDcW6SRsk7XtjvNkj49C2-o-_BmQywYizh=QOvu5z16iw@mail.gmail.com>

I bisected from 5.4.2 to HEAD. The core is fully repeatable. It's a
larger script (zplugin) operation that causes the core, so currently
this is kind of a black box.

f7519811e1bbe990ff1c3d499ffb70cfc2d034f8 is the first bad commit
commit f7519811e1bbe990ff1c3d499ffb70cfc2d034f8
Author: Ricardo Giorni <ricardo@giorni.co>
Date:   Sun Apr 29 12:05:39 2018 -0700

    47201: fix 42355 for multiple backslashes


I think this is a well pointed commit, because any backtrace I
occurred was going through zshlex:

    ...
    frame #5: 0x00007fff5766b256 libsystem_malloc.dylib`free_tiny + 628
    frame #6: 0x0000000100e076e8 zsh`zfree + 24
    frame #7: 0x0000000100dc4c3c zsh`gethere + 780
    frame #8: 0x0000000100dfafc1 zsh`zshlex + 369
    frame #9: 0x0000000100e26c6f zsh`par_redir + 655
    frame #10: 0x0000000100e29b5f zsh`par_simple + 2063
    ...


On 2 July 2018 at 12:09, Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> Hello,
> I've triggered loading a snippet with Zplugin, and core happened.
> Tried again and it repeats. Zsh-5.5.1-dev-0, HEAD. Don't have energy
> currently to track this, maybe someone has idea for a "economical"
> debug print or other thing to reveal the cause?
>
> frame #0: 0x00000001092f7e1f
> zsh-5.5.1-dev-0`scanmatchtable(ht=<unavailable>,
> pprog=0x0000000000000000, sorted=446721, flags1=0, flags2=0,
> scanfunc=(zsh-5.5.1-dev-0`scanendscope at params.c:5570), scanflags=0)
> at hashtable.c:424 [opt]
>    421         for (i = 0; i < hsize; i++)
>    422             for (st.u.u = nodes[i]; st.u.u; ) {
>    423             HashNode hn = st.u.u;
> -> 424             st.u.u = st.u.u->next;
>    425             if ((!flags1 || (hn->flags & flags1)) &&
> !(hn->flags & flags2)
>    426                 && (!pprog || pattry(pprog, hn->nam))) {
>    427                 match++;
>
> --
> Sebastian Gniazdowski
> News: https://twitter.com/ZdharmaI
> IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin



-- 
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin


  reply	other threads:[~2018-07-05 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 10:09 Sebastian Gniazdowski
2018-07-05 13:40 ` Sebastian Gniazdowski [this message]
2018-07-10 13:33   ` Peter Stephenson
     [not found]   ` <20180710143319.340e1bdf@camnpupstephen.cam.scsc.local>
2018-07-10 13:38     ` Peter Stephenson
2018-07-10 15:12       ` Sebastian Gniazdowski

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=CAKc7PVBQn-ZjZ1T0TLqofETRiRw3xTExJ3aN10FWPqEQSi180w@mail.gmail.com \
    --to=sgniazdowski@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).