zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: "Larry P. Schrof" <larry@schrof.net>,
	zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: (Revisited): zsh + less == hard hang of tty.
Date: Tue, 26 Sep 2006 18:00:39 +0100	[thread overview]
Message-ID: <200609261700.k8QH0eVd001791@news01.csr.com> (raw)
In-Reply-To: <20060926142946.GA1608@lucien.blight.com>

"Larry P. Schrof" wrote:
> When in zsh, if I do: less <some_file>, the terminal HARD HANGS.

It sounds like this is reproducible in your case.  Since this doesn't
seem to be a general problem, we need to find out what's different.

Does the same happen with

  zsh -c 'less <file>'

or, if not, with

  zsh -ic 'less <file>'

(which has interactive handling turned on)?  If so, the last few entries
you get with "strace" in front of the appropriate one might be
interesting.  You might get a huge amount of output in the second case
owing to initialisation files.

Otherwise, use gdb to attach to the hung process in question.  This is
most useful if zsh was compiled with debugging (configure
--enable-zsh-debug does that).

% gdb zsh
(gdb) attach 14183
(gdb) bt

However, it might actually be hung in less and zsh is simply waiting for
that to finish.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php


       reply	other threads:[~2006-09-26 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060926142946.GA1608@lucien.blight.com>
2006-09-26 17:00 ` Peter Stephenson [this message]
2006-09-26 17:26   ` Larry P. Schrof
2006-09-26 17:50     ` Peter Stephenson
2006-09-26 18:15       ` Andrey Borzenkov
2006-09-26 19:05         ` Larry P. Schrof
2006-09-27  2:43           ` Andrey Borzenkov

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=200609261700.k8QH0eVd001791@news01.csr.com \
    --to=pws@csr.com \
    --cc=larry@schrof.net \
    --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).