From: Dan Nelson <dnelson@allantgroup.com>
To: Mark Daniel Reidel <mark@reidel.info>
Cc: zsh-workers@sunsite.dk
Subject: Re: Pause when quitting under FreeBSD
Date: Tue, 26 Jul 2005 17:30:39 -0500 [thread overview]
Message-ID: <20050726223038.GC57412@dan.emsphone.com> (raw)
In-Reply-To: <42E6D3E6.5070206@reidel.info>
In the last episode (Jul 27), Mark Daniel Reidel said:
> I'm not 100% sure if this is the right place to post this problem,
> but ever since I switched to a 64bit OS and installed my shell of
> choice, quitting zsh suddenly takes about 2 or 3 seconds. Since my
> configuration comes from an NFS-server, I can be 100% sure that it's
> the same unter FreeBSD 5.4 and 6 (which is the one that seems to have
> problems). I already tried a ktrace to maybe find the bugger, but the
> time-consumption seems to be during some breaks. Here's the important
> parts:
>
> [...]
> 744 zsh Events dropped.
> 744 zsh 1122421279.260961 RET open 3
> 744 zsh Events dropped.
> 744 zsh 1122421279.271187 RET close 0
> 744 zsh 1122421280.524404 CALL break(0x876c20)
> 744 zsh 1122421280.524420 RET break 0
> 744 zsh 1122421280.563815 CALL break(0x871c20)
> [...]
> 744 zsh 1122421281.009755 CALL break(0x835c20)
If you can switch to another shell quickly and kill -STOP it, you
should be able to attach a gdb session and get a stack trace. Or, run
gcore on it (which will SIGSTOP it temporarily) and gdb the resulting
corefile. Since the next thing zsh does is unlink the history
lockfile, I'd guess the problem is hist.c:hend() or savehistfile()
somewhere. Take a look at your ~/.zsh_history file; do you maybe have
some really really long lines in it? Maybe an NFS glitch caused a run
of NULLs to get stored in there.
> 744 zsh 1122421281.009771 RET break 0
> 744 zsh 1122421281.548473 CALL break(0x7d4c20)
> 744 zsh 1122421281.548534 RET break 0
> 744 zsh 1122421281.548602 CALL unlink(0x7b6960)
> 744 zsh 1122421281.548606 NAMI "/home/mark/.zsh_history.LOCK"
> 744 zsh 1122421281.553918 RET unlink 0
> [...]
--
Dan Nelson
dnelson@allantgroup.com
next prev parent reply other threads:[~2005-07-26 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 0:23 Mark Daniel Reidel
2005-07-26 22:30 ` Dan Nelson [this message]
2005-07-27 0:37 ` Mark Daniel Reidel
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=20050726223038.GC57412@dan.emsphone.com \
--to=dnelson@allantgroup.com \
--cc=mark@reidel.info \
--cc=zsh-workers@sunsite.dk \
/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).