zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [BUG] sigsegv
Date: Tue, 25 Apr 2023 13:48:04 +0000	[thread overview]
Message-ID: <CAKc7PVDw98bvTSNWo4q52ZJ=i8vhRooKZHb-mOzenJVMoe1MFg@mail.gmail.com> (raw)

I have to say that current HEAD has many sigsegv errors, at least twp.
The reported in this email is an older problem with alt-/ history
complete, I've had it also with 5.8. I'm still waiting for the 5.9
only problem to occur, it's quite random and hard to reproduce.
To trigger the error, press alt-/ some times.

#0  0x0000000000457868 in insertlinknode (list=list@entry=0x7ffff7abe368,
    node=0x7ffff55600d8, dat=0x7ffff556e8f0) at linklist.c:137
#1  0x00007ffff7bed6bf in histwgetfn (pm=<optimized out>) at parameter.c:1241
#2  0x0000000000467c46 in getvaluearr (v=0x7ffffffe79e0) at params.c:690
#3  0x0000000000467fe5 in getvaluearr (v=0x7ffffffe79e0) at params.c:2503
#4  getarrvalue (v=v@entry=0x7ffffffe79e0) at params.c:2470
#5  0x000000000048d24f in paramsubst (ret_flags=0x7ffffffe7ae4, pf_flags=4,
    qt=0, str=0x7ffffffe7970, n=0x7ffffffe7dd0, l=<optimized out>)
    at subst.c:2712
#6  stringsubst (list=list@entry=0x7ffffffe7d30, node=0x7ffffffe7dd0,
    pf_flags=pf_flags@entry=4, ret_flags=ret_flags@entry=0x7ffffffe7ae4,
    asssub=asssub@entry=0) at subst.c:322
#7  0x0000000000492595 in prefork (list=list@entry=0x7ffffffe7d30,
    flags=flags@entry=6, ret_flags=0x7ffffffe7ae4, ret_flags@entry=0x0)
    at subst.c:142
#8  0x000000000043083e in execcmd_exec (state=state@entry=0x7ffffffe91d0,
    eparams=eparams@entry=0x7ffffffe8e50, input=input@entry=0,
    output=output@entry=0, how=<optimized out>, how@entry=2,
    last1=<optimized out>, last1@entry=2, close_if_forked=-1) at exec.c:4138
#9  0x000000000043091e in execpline2 (state=state@entry=0x7ffffffe91d0,
    pcode=pcode@entry=1283, how=how@entry=2, input=0, output=0,
    last1=last1@entry=0) at exec.c:2003
#10 0x0000000000430c66 in execpline (state=state@entry=0x7ffffffe91d0,
    slcode=<optimized out>, how=how@entry=2, last1=0) at exec.c:1728
#11 0x000000000043243b in execlist (state=state@entry=0x7ffffffe91d0,
    dont_change_job=dont_change_job@entry=1, exiting=exiting@entry=0)
    at exec.c:1482
#12 0x0000000000432c32 in execode (p=0x146e1b0,
    dont_change_job=dont_change_job@entry=1, exiting=exiting@entry=0,
    context=context@entry=0x4a52c3 "loadautofunc") at exec.c:1263
#13 0x000000000043609d in execautofn_basic (do_exec=<optimized out>,
    state=<optimized out>, state=<optimized out>) at exec.c:5578
#14 0x00000000004302d6 in execcmd_exec (state=state@entry=0x7ffffffea860,
    eparams=eparams@entry=0x7ffffffea4e0, input=input@entry=0,
    output=output@entry=0, how=<optimized out>, how@entry=18,
    last1=last1@entry=2, close_if_forked=-1) at exec.c:4005
#15 0x000000000043091e in execpline2 (state=state@entry=0x7ffffffea860,
    pcode=pcode@entry=3, how=how@entry=18, input=0, output=0,
last1=last1@entry=0) at exec.c:2003
#16 0x0000000000430c66 in execpline (state=state@entry=0x7ffffffea860,
    slcode=<optimized out>, how=how@entry=18, last1=0) at exec.c:1728
#17 0x000000000043243b in execlist (state=state@entry=0x7ffffffea860,
    dont_change_job=dont_change_job@entry=1, exiting=exiting@entry=0)
    at exec.c:1482
#18 0x0000000000432c32 in execode (p=p@entry=0x590c10,
    dont_change_job=dont_change_job@entry=1, exiting=exiting@entry=0,
    context=context@entry=0x4a5263 "shfunc") at exec.c:1263
#19 0x0000000000433b82 in runshfunc (prog=prog@entry=0x590c10,
    wrap=wrap@entry=0x0, name=name@entry=0x7ffff7abe168 "_history")
    at exec.c:6148
#20 0x00007ffff7e48c6b in comp_wrapper (name=0x7ffff7abe168 "_history",
    w=0x0, prog=0x590c10) at complete.c:1588
#21 comp_wrapper (prog=0x590c10, w=0x0, name=0x7ffff7abe168 "_history")
    at complete.c:1553
#22 0x00000000004337ed in runshfunc (prog=0x590c10,
    wrap=0x7ffff7e64720 <wrapper>, name=0x7ffff7abe168 "_history")
    at exec.c:6132
…
…
(gdb) frame
#0  0x0000000000457868 in insertlinknode (list=list@entry=0x7ffff7abe368,
    node=0x7ffff55600d8, dat=0x7ffff556e8f0) at linklist.c:137
137         tmp = node->next;
(gdb) p node
$1 = (LinkNode) 0x7ffff55600d8
(gdb) p *node
Cannot access memory at address 0x7ffff55600d8

-- 
Best regards,
Sebastian Gniazdowski


             reply	other threads:[~2023-04-25 13:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 13:48 Sebastian Gniazdowski [this message]
2023-04-25 13:56 ` Peter Stephenson
2023-04-28 11:25   ` Sebastian Gniazdowski
2023-04-28 11:41     ` Peter Stephenson
2023-04-28 14:13       ` Sebastian Gniazdowski
2023-04-28 14:22         ` Peter Stephenson
2023-04-29 10:52           ` Sebastian Gniazdowski
2023-04-30  9:51             ` Sebastian Gniazdowski
2023-04-30 17:30             ` Peter Stephenson
2023-05-03 15:35               ` Sebastian Gniazdowski
2023-05-03 15:56                 ` Sebastian Gniazdowski
2023-05-03 16:25                 ` Peter Stephenson
2023-05-03 21:13                   ` Bart Schaefer
     [not found]                     ` <CAKc7PVDt6hS26DxC3hDE-ziMXm-K1jqbJXghynpp-ZhpdN_LLw@mail.gmail.com>
2023-05-04 15:01                       ` Bart Schaefer
2023-05-05 18:54                   ` Peter Stephenson

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='CAKc7PVDw98bvTSNWo4q52ZJ=i8vhRooKZHb-mOzenJVMoe1MFg@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).