zsh-workers
 help / color / mirror / code / Atom feed
* 5.9 core dumps under zleentry->zleread->zlecore
@ 2022-06-02  7:11 Johan Ström
  2022-06-02  7:31 ` Bart Schaefer
  2022-06-03  7:14 ` Jun T
  0 siblings, 2 replies; 10+ messages in thread
From: Johan Ström @ 2022-06-02  7:11 UTC (permalink / raw)
  To: zsh-workers

Hi,

I've reported some core dumps in 5.8.1 earlier (never had any in 5.8; 
see previous thread). Now upgraded to 5.9, and similar behavior, after 
some idle periods of some days, returned to terminal and at first use, 
it crashed. Happened to two terminals, different but similar traces (see 
below). Not sure about any console output as terminal window closed 
before I could notice.

Not subscribed to list (to high volume), please include me in direct 
mail for any follow ups (I hope this reaches the list anyway; I haven't 
found any ticket system so I guess this is appropriate way to report bugs?).

Regards
Johan

-----

            PID: 1097282 (zsh)
            UID: 1000 (johan)
            GID: 1001 (johan)
         Signal: 6 (ABRT)
      Timestamp: Thu 2022-06-02 08:27:39 CEST (1min 12s ago)
   Command Line: /usr/bin/zsh
     Executable: /usr/bin/zsh
  Control Group: /user.slice/user-1000.slice/session-1.scope
           Unit: session-1.scope
          Slice: user-1000.slice
        Session: 1
      Owner UID: 1000 (johan)
        Boot ID: a033b8f5156d4e4289dcaefa16f0df16
     Machine ID: 321bfe907bef49b9a7b0d61fc2ee69c7
       Hostname: johan-amd
        Storage: 
/var/lib/systemd/coredump/core.zsh.1000.a033b8f5156d4e4289dcaefa16f0df16.1097282.1654151259000000.zst 
(present)
      Disk Size: 411.2K
        Message: Process 1097282 (zsh) of user 1000 dumped core.

                 Module linux-vdso.so.1 with build-id 
c4fab7a7ee86e62a6272cb22354ad5a06fbf1a5d
                 Module computil.so with build-id 
6ee1c6257c5fa3dfefd87799a2abdf8a409c39c5
                 Module rlimits.so with build-id 
2c91e60448a33848c943bc0b9de03c3ca14ea6aa
                 Module stat.so with build-id 
0df82bdf6bd6c5fb828c9927cbef935803c6fd94
                 Module parameter.so with build-id 
2a9a5e258c97a703328f88809eb4cf7cd17193d0
                 Module zutil.so with build-id 
5f423a575063581ffb93c61a1242c56a1f2d9421
                 Module complete.so with build-id 
f126a758351b630931cd6dfd1a23f26ac71b40d7
                 Module zle.so with build-id 
c81f446d1ef258c04580ce73fcf46b00e4baf193
                 Module ld-linux-x86-64.so.2 with build-id 
fc93487393eea02b5bc6e76e48976fc325294c24
                 Module libc.so.6 with build-id 
388993b6ef62f964bc7bf473c069fbfe957b9e44
                 Module libm.so.6 with build-id 
210ec9905e41825671210f8f7d0b24d6c371196a
                 Module libncursesw.so.6 with build-id 
b9917757481e6fa6097e2a1f31f5bb5eaf138c4e
                 Module libcap.so.2 with build-id 
21b00ab76bb16fde56fd741f07233c78069f0579
                 Module zsh with build-id 
6cec2c2b43e208d3358bb897a2896a074d451cef
                 Stack trace of thread 1097282:
                 #0  0x00007fb08ae6c36c n/a (libc.so.6 + 0x8e36c)
                 #1  0x00007fb08ae1c838 raise (libc.so.6 + 0x3e838)
                 #2  0x00007fb08ae06535 abort (libc.so.6 + 0x28535)
                 #3  0x00007fb08ae6045e n/a (libc.so.6 + 0x8245e)
                 #4  0x00007fb08ae760cc n/a (libc.so.6 + 0x980cc)
                 #5  0x00007fb08ae76c0e n/a (libc.so.6 + 0x98c0e)
                 #6  0x00007fb08ae76d85 n/a (libc.so.6 + 0x98d85)
                 #7  0x00007fb08ae78e9f n/a (libc.so.6 + 0x9ae9f)
                 #8  0x00007fb08ae7a47a malloc (libc.so.6 + 0x9c47a)
                 #9  0x000055ff7ab040f8 zalloc (zsh + 0x730f8)
                 #10 0x00007fb08a549417 calclist (complete.so + 0x1b417)
                 #11 0x00007fb08a54b040 ilistmatches (complete.so + 0x1d040)
                 #12 0x00007fb08a543eb1 list_matches (complete.so + 0x15eb1)
                 #13 0x00007fb08a5821cf zrefresh (zle.so + 0x2c1cf)
                 #14 0x00007fb08a5767e7 zlecore (zle.so + 0x207e7)
                 #15 0x00007fb08a577514 zleread (zle.so + 0x21514)
                 #16 0x000055ff7aaf7874 zleentry (zsh + 0x66874)
                 #17 0x000055ff7aaf80f6 ingetc (zsh + 0x670f6)
                 #18 0x000055ff7aaeafe4 n/a (zsh + 0x59fe4)
                 #19 0x000055ff7ab05e5f n/a (zsh + 0x74e5f)
                 #20 0x000055ff7ab28ad8 parse_event (zsh + 0x97ad8)
                 #21 0x000055ff7aaf13d6 loop (zsh + 0x603d6)
                 #22 0x000055ff7aaf9865 zsh_main (zsh + 0x68865)
                 #23 0x000055ff7aaa80ee main (zsh + 0x170ee)
                 #24 0x00007fb08ae07290 n/a (libc.so.6 + 0x29290)
                 #25 0x00007fb08ae0734a __libc_start_main (libc.so.6 + 
0x2934a)
                 #26 0x000055ff7aaa8115 _start (zsh + 0x17115)
                 ELF object binary architecture: AMD x86-64


-----


            PID: 2195627 (zsh)
            UID: 1000 (johan)
            GID: 1001 (johan)
         Signal: 6 (ABRT)
      Timestamp: Thu 2022-06-02 07:37:08 CEST (55min ago)
   Command Line: /usr/bin/zsh
     Executable: /usr/bin/zsh
  Control Group: /user.slice/user-1000.slice/session-1.scope
           Unit: session-1.scope
          Slice: user-1000.slice
        Session: 1
      Owner UID: 1000 (johan)
        Boot ID: a033b8f5156d4e4289dcaefa16f0df16
     Machine ID: 321bfe907bef49b9a7b0d61fc2ee69c7
       Hostname: johan-amd
        Storage: 
/var/lib/systemd/coredump/core.zsh.1000.a033b8f5156d4e4289dcaefa16f0df16.2195627.1654148228000000.zst 
(present)
      Disk Size: 449.7K
        Message: Process 2195627 (zsh) of user 1000 dumped core.

                 Module linux-vdso.so.1 with build-id 
c4fab7a7ee86e62a6272cb22354ad5a06fbf1a5d
                 Module computil.so with build-id 
6ee1c6257c5fa3dfefd87799a2abdf8a409c39c5
                 Module rlimits.so with build-id 
2c91e60448a33848c943bc0b9de03c3ca14ea6aa
                 Module stat.so with build-id 
0df82bdf6bd6c5fb828c9927cbef935803c6fd94
                 Module parameter.so with build-id 
2a9a5e258c97a703328f88809eb4cf7cd17193d0
                 Module zutil.so with build-id 
5f423a575063581ffb93c61a1242c56a1f2d9421
                 Module complete.so with build-id 
f126a758351b630931cd6dfd1a23f26ac71b40d7
                 Module zle.so with build-id 
c81f446d1ef258c04580ce73fcf46b00e4baf193
                 Module ld-linux-x86-64.so.2 with build-id 
fc93487393eea02b5bc6e76e48976fc325294c24
                 Module libc.so.6 with build-id 
388993b6ef62f964bc7bf473c069fbfe957b9e44
                 Module libm.so.6 with build-id 
210ec9905e41825671210f8f7d0b24d6c371196a
                 Module libncursesw.so.6 with build-id 
b9917757481e6fa6097e2a1f31f5bb5eaf138c4e
                 Module libcap.so.2 with build-id 
21b00ab76bb16fde56fd741f07233c78069f0579
                 Module zsh with build-id 
6cec2c2b43e208d3358bb897a2896a074d451cef
                 Stack trace of thread 2195627:
                 #0  0x00007f2f9358836c n/a (libc.so.6 + 0x8e36c)
                 #1  0x00007f2f93538838 raise (libc.so.6 + 0x3e838)
                 #2  0x00007f2f93522535 abort (libc.so.6 + 0x28535)
                 #3  0x00007f2f9357c45e n/a (libc.so.6 + 0x8245e)
                 #4  0x00007f2f935920cc n/a (libc.so.6 + 0x980cc)
                 #5  0x00007f2f9359425c n/a (libc.so.6 + 0x9a25c)
                 #6  0x00007f2f935968f3 free (libc.so.6 + 0x9c8f3)
                 #7  0x00007f2f92ca0084 zrefresh (zle.so + 0x2e084)
                 #8  0x00007f2f92c94d8e n/a (zle.so + 0x22d8e)
                 #9  0x000055d4a9fc3874 zleentry (zsh + 0x66874)
                 #10 0x000055d4aa005493 zhandler (zsh + 0xa8493)
                 #11 0x00007f2f935388e0 n/a (libc.so.6 + 0x3e8e0)
                 #12 0x00007f2f935fbef2 read (libc.so.6 + 0x101ef2)
                 #13 0x00007f2f92c8c3dc getbyte (zle.so + 0x1a3dc)
                 #14 0x00007f2f92c8ccb1 getkeymapcmd (zle.so + 0x1acb1)
                 #15 0x00007f2f92c8f819 getkeycmd (zle.so + 0x1d819)
                 #16 0x00007f2f92c9270d zlecore (zle.so + 0x2070d)
                 #17 0x00007f2f92c93514 zleread (zle.so + 0x21514)
                 #18 0x000055d4a9fc3874 zleentry (zsh + 0x66874)
                 #19 0x000055d4a9fc40f6 ingetc (zsh + 0x670f6)
                 #20 0x000055d4a9fb6fe4 n/a (zsh + 0x59fe4)
                 #21 0x000055d4a9fd1e5f n/a (zsh + 0x74e5f)
                 #22 0x000055d4a9ff4ad8 parse_event (zsh + 0x97ad8)
                 #23 0x000055d4a9fbd3d6 loop (zsh + 0x603d6)
                 #24 0x000055d4a9fc5865 zsh_main (zsh + 0x68865)
                 #25 0x000055d4a9f740ee main (zsh + 0x170ee)
                 #26 0x00007f2f93523290 n/a (libc.so.6 + 0x29290)
                 #27 0x00007f2f9352334a __libc_start_main (libc.so.6 + 
0x2934a)
                 #28 0x000055d4a9f74115 _start (zsh + 0x17115)
                 ELF object binary architecture: AMD x86-64
-----



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-02  7:11 5.9 core dumps under zleentry->zleread->zlecore Johan Ström
@ 2022-06-02  7:31 ` Bart Schaefer
  2022-06-02  9:25   ` Johan Ström
  2022-06-03  7:14 ` Jun T
  1 sibling, 1 reply; 10+ messages in thread
From: Bart Schaefer @ 2022-06-02  7:31 UTC (permalink / raw)
  To: Johan Ström; +Cc: Zsh hackers list

The end of the previous thread was that you had valgrind running, but
we never heard any more from you after one report that was considered
a false positive.

We're going to need some more info on this, I fear -- would it at
least be possible for you to configure --enable-zsh-debug and
recompile, so that you get a stack trace with line numbers?


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-02  7:31 ` Bart Schaefer
@ 2022-06-02  9:25   ` Johan Ström
  0 siblings, 0 replies; 10+ messages in thread
From: Johan Ström @ 2022-06-02  9:25 UTC (permalink / raw)
  To: Bart Schaefer; +Cc: Zsh hackers list

On 2022-06-02 09:31, Bart Schaefer wrote:
> The end of the previous thread was that you had valgrind running, but
> we never heard any more from you after one report that was considered
> a false positive.
I think I submitted at least one valgrind post of initial warnings, 
which was probably bogus, but then I didn't really manage to reproduce 
it unfortunately, and it kind of got forgotten.
>
> We're going to need some more info on this, I fear -- would it at
> least be possible for you to configure --enable-zsh-debug and
> recompile, so that you get a stack trace with line numbers?

I've cloned 
https://github.com/archlinux/svntogit-packages/tree/packages/zsh/trunk 
now and added --enable-zsh-debug.
Running with that now, will report back if it crashes again.


During make check one failure occurred though, had to skip 'make check':

Testing multibyte with locale en_US.UTF-8
--- /tmp/zsh.ztst.4900/ztst.err    2022-06-02 11:12:41.488316802 +0200
+++ /tmp/zsh.ztst.4900/ztst.terr    2022-06-02 11:12:41.488316802 +0200
@@ -1 +1 @@
-./test_bad_param:1: command not found: $\M-i#
+./test_bad_param:1: invalid or incomplete multibyte or wide character: 
$\M-i#
Test ./D07multibyte.ztst failed: error output differs from expected as 
shown above for:
   # The following doesn't necessarily need UTF-8, but this gives
   # us the full effect --- if we parse this wrongly the \xe9
   # in combination with the tokenized input afterwards looks like a
   # valid UTF-8 character.  But it isn't.
   print $'$\xe9#``' >test_bad_param
   (setopt nonomatch
   . ./test_bad_param)
Was testing: Invalid parameter name with following tokenized input
./D07multibyte.ztst: test failed.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-02  7:11 5.9 core dumps under zleentry->zleread->zlecore Johan Ström
  2022-06-02  7:31 ` Bart Schaefer
@ 2022-06-03  7:14 ` Jun T
  2022-06-03  7:19   ` Johan Ström
  1 sibling, 1 reply; 10+ messages in thread
From: Jun T @ 2022-06-03  7:14 UTC (permalink / raw)
  To: zsh-workers; +Cc: Johan Ström


> 2022/06/02 16:11, Johan Ström <johan@stromnet.se> wrote:
> 
> Now upgraded to 5.9, and similar behavior, after some idle periods of some days, returned to terminal and at first use, it crashed.

It seems that you get core dumps after "upgrede".
How did you upgrade your zsh?  By 'pacman -Syu' ?
If so, have you rebooted your OS after the upgrade?

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-03  7:14 ` Jun T
@ 2022-06-03  7:19   ` Johan Ström
  2022-06-03  9:53     ` Jun T
  0 siblings, 1 reply; 10+ messages in thread
From: Johan Ström @ 2022-06-03  7:19 UTC (permalink / raw)
  To: Jun T, zsh-workers

On 2022-06-03 09:14, Jun T wrote:
>> 2022/06/02 16:11, Johan Ström <johan@stromnet.se> wrote:
>>
>> Now upgraded to 5.9, and similar behavior, after some idle periods of some days, returned to terminal and at first use, it crashed.
> It seems that you get core dumps after "upgrede".
> How did you upgrade your zsh?  By 'pacman -Syu' ?
> If so, have you rebooted your OS after the upgrade?

Yes, full system update including reboot:

[2021-07-30T11:37:51+0200] [ALPM] installed zsh (5.8-1)
[2022-02-16T08:14:00+0100] [ALPM] upgraded zsh (5.8-1 -> 5.8.1-1)
[2022-05-11T18:36:51+0200] [ALPM] upgraded zsh (5.8.1-1 -> 5.8.1-2)
[2022-05-26T11:01:13+0200] [ALPM] upgraded zsh (5.8.1-2 -> 5.9-1)
[2022-06-02T11:23:37+0200] [ALPM] reinstalled zsh (5.9-1)   # this was 
my install of the debug-enabled package

Before 5.8.1 (16'th feb) I never had any issues with zsh.
Haven't made any changes to .zshrc (posted in previous thread) at all 
before or after (but I cannot say for sure if some other package's zsh 
additions (/usr/share/zsh/site-functions?) might have been altered).



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-03  7:19   ` Johan Ström
@ 2022-06-03  9:53     ` Jun T
  2022-06-03 10:02       ` Johan Ström
  0 siblings, 1 reply; 10+ messages in thread
From: Jun T @ 2022-06-03  9:53 UTC (permalink / raw)
  To: zsh-workers; +Cc: Johan Ström


> 2022/06/03 16:19, Johan Ström <johan@stromnet.se> wrote:
> 
> Yes, full system update including reboot:

Hmm, then:

pacman -Syu
Reboot.
Start a new zsh, leave it for a few days, and then it cashes.
After the crash, start another zsh, but it doesn't crash.

Is this what happening to you?

> During make check one failure occurred though, had to skip 'make check':

I can't reproduce this.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-03  9:53     ` Jun T
@ 2022-06-03 10:02       ` Johan Ström
  2022-06-04  3:32         ` Bart Schaefer
  0 siblings, 1 reply; 10+ messages in thread
From: Johan Ström @ 2022-06-03 10:02 UTC (permalink / raw)
  To: Jun T, zsh-workers


On 2022-06-03 11:53, Jun T wrote:
>> 2022/06/03 16:19, Johan Ström <johan@stromnet.se> wrote:
>>
>> Yes, full system update including reboot:
> Hmm, then:
>
> pacman -Syu
> Reboot.
> Start a new zsh, leave it for a few days, and then it cashes.
> After the crash, start another zsh, but it doesn't crash.
>
> Is this what happening to you?

The terminals (https://codeberg.org/dnkl/foot) where used a bit on one 
day, then left idle for some days, then as soon as touching it (cannot 
say for sure, up-arrow or enter or something), the zsh process crashed.
Other terminals with similar workload have remained alive, so it seems 
to be a bit random. All terminals where probably started around the same 
time (i.e. similar history file read in?), but cannot say for sure.
Not same commands executed in them, most work in them are of the 
"up-arrow/search-in-history -re-execute" style, but of course some "new" 
commands executed too.

No other process crashes / problems indicating machine-wide issues.

It doesn't happen super often, but every now and then:

$ coredumpctl |grep -E 'zsh|TIME'
TIME                             PID  UID  GID SIG     COREFILE EXE SIZE
Tue 2022-03-01 08:44:43 CET  1530870 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Fri 2022-03-04 08:29:11 CET  1530829 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Fri 2022-03-04 09:28:11 CET  2161402 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:29:04 CET  2080740 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:29:28 CET   844046 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:29:34 CET   881888 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:30:03 CET   843836 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:45:46 CET   987956 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 09:12:02 CET   835401 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-22 07:37:58 CET  2751972 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-22 07:38:50 CET   636567 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-22 08:40:14 CET   505887 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-12 07:48:54 CEST 2560148 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-12 09:28:53 CEST  845636 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-19 08:41:26 CEST 2828220 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-19 08:41:36 CEST  506222 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Mon 2022-05-02 06:55:52 CEST 1776915 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-05-24 07:32:32 CEST 2358112 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-05-24 08:12:13 CEST 1088984 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-05-24 10:16:54 CEST 2983454 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Thu 2022-06-02 07:37:08 CEST 2195627 1000 1001 SIGABRT present 
/usr/bin/zsh 449.7K
Thu 2022-06-02 08:27:39 CEST 1097282 1000 1001 SIGABRT present 
/usr/bin/zsh 411.2K



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-03 10:02       ` Johan Ström
@ 2022-06-04  3:32         ` Bart Schaefer
  2022-06-04  7:39           ` Johan Ström
  0 siblings, 1 reply; 10+ messages in thread
From: Bart Schaefer @ 2022-06-04  3:32 UTC (permalink / raw)
  To: Johan Ström; +Cc: Jun T, Zsh hackers list

On Fri, Jun 3, 2022 at 3:03 AM Johan Ström <johan@stromnet.se> wrote:
>
> The terminals (https://codeberg.org/dnkl/foot) where used a bit on one
> day, then left idle for some days, then as soon as touching it (cannot
> say for sure, up-arrow or enter or something), the zsh process crashed.
> Other terminals with similar workload have remained alive, so it seems
> to be a bit random.

I would start looking for signals that your terminal (or wayland)
might be sending.  E.g., if this happens to windows that were on
different virtual desktops or that were partly or completely hidden
behind other windows or that were minimized and then popped open, the
shell may be getting a lot of SIGWINCH signals.

The other thing I notice is that the configure options in the arch
linux package you used include enabling global startup scripts in
/etc/zsh/, and explicitly enable sourcing /etc/profile.  Is there
anything (else) in your /etc/zsh/ directory?


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-04  3:32         ` Bart Schaefer
@ 2022-06-04  7:39           ` Johan Ström
  2022-06-04 20:06             ` Bart Schaefer
  0 siblings, 1 reply; 10+ messages in thread
From: Johan Ström @ 2022-06-04  7:39 UTC (permalink / raw)
  To: Bart Schaefer; +Cc: Jun T, Zsh hackers list

On 2022-06-04 05:32, Bart Schaefer wrote:
> On Fri, Jun 3, 2022 at 3:03 AM Johan Ström <johan@stromnet.se> wrote:
>> The terminals (https://codeberg.org/dnkl/foot) where used a bit on one
>> day, then left idle for some days, then as soon as touching it (cannot
>> say for sure, up-arrow or enter or something), the zsh process crashed.
>> Other terminals with similar workload have remained alive, so it seems
>> to be a bit random.
> I would start looking for signals that your terminal (or wayland)
> might be sending.  E.g., if this happens to windows that were on
> different virtual desktops or that were partly or completely hidden
> behind other windows or that were minimized and then popped open, the
> shell may be getting a lot of SIGWINCH signals.
Hm, I had cases where terminals have been on the same virtual desktop, 
with no re-arranging going on at the moment, or since last being used 
(basically only resuming work in existing windows).
Not sure if SIGWINCH would be sent by just switching virtual desktop (sway).
>
> The other thing I notice is that the configure options in the arch
> linux package you used include enabling global startup scripts in
> /etc/zsh/, and explicitly enable sourcing /etc/profile.  Is there
> anything (else) in your /etc/zsh/ directory?
In /etc/zsh, only zprofile: 
https://github.com/archlinux/svntogit-packages/blob/packages/zsh/trunk/zprofile
Which references this: 
https://github.com/archlinux/svntogit-packages/blob/packages/filesystem/trunk/profile


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: 5.9 core dumps under zleentry->zleread->zlecore
  2022-06-04  7:39           ` Johan Ström
@ 2022-06-04 20:06             ` Bart Schaefer
  0 siblings, 0 replies; 10+ messages in thread
From: Bart Schaefer @ 2022-06-04 20:06 UTC (permalink / raw)
  To: Johan Ström; +Cc: Jun T, Zsh hackers list

On Sat, Jun 4, 2022 at 12:39 AM Johan Ström <johan@stromnet.se> wrote:
>
> Hm, I had cases where terminals have been on the same virtual desktop,
> with no re-arranging going on at the moment, or since last being used
> (basically only resuming work in existing windows).
> Not sure if SIGWINCH would be sent by just switching virtual desktop (sway).

One reason I'm speculating about this is because of this from your
previous stack trace:

                 #9  0x000055ff7ab040f8 zalloc (zsh + 0x730f8)
                 #10 0x00007fb08a549417 calclist (complete.so + 0x1b417)
                 #11 0x00007fb08a54b040 ilistmatches (complete.so + 0x1d040)

There's only one zalloc() in calclist:

            ws = g->widths = (int *) zalloc(zterm_columns * sizeof(int));

If zterm_columns has somehow become messed up, this might run you out of memory.

Then in the other trace you have:

                 #10 0x000055d4aa005493 zhandler (zsh + 0xa8493)
                 #11 0x00007f2f935388e0 n/a (libc.so.6 + 0x3e8e0)
                 #12 0x00007f2f935fbef2 read (libc.so.6 + 0x101ef2)

That definitely means a signal was received, and SIGWINCH is
explicitly unblocked around that read() call, but it goes straight on
to:

                 #9  0x000055d4a9fc3874 zleentry (zsh + 0x66874)

The only way to get to that from a signal handler is when a
user-defined trap is run:

    /*
     * If zle was running while the trap was executed, see if we
     * need to restore the display.
     */
    if (zleactive && resetneeded)
        zleentry(ZLE_CMD_REFRESH);

However (I suspect) the compiler has optimized out a couple of
intervening function calls, which is why I hope you can get this to
reoccur with a debug build.

> In /etc/zsh, only zprofile:
> https://github.com/archlinux/svntogit-packages/blob/packages/zsh/trunk/zprofile
> Which references this:
> https://github.com/archlinux/svntogit-packages/blob/packages/filesystem/trunk/profile

Yes, which does
  emulate sh -c 'source /etc/profile'
though it seems unlikely that anything too weird is coming in that way.


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2022-06-04 20:07 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-02  7:11 5.9 core dumps under zleentry->zleread->zlecore Johan Ström
2022-06-02  7:31 ` Bart Schaefer
2022-06-02  9:25   ` Johan Ström
2022-06-03  7:14 ` Jun T
2022-06-03  7:19   ` Johan Ström
2022-06-03  9:53     ` Jun T
2022-06-03 10:02       ` Johan Ström
2022-06-04  3:32         ` Bart Schaefer
2022-06-04  7:39           ` Johan Ström
2022-06-04 20:06             ` Bart Schaefer

Code repositories for project(s) associated with this 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).