From: Peter Stephenson <pws@csr.com>
To: "Murilo Opsfelder Araújo" <mopsfelder@gmail.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: zsh seg fault when TERM = linux
Date: Tue, 5 May 2009 16:36:20 +0100 [thread overview]
Message-ID: <20090505163620.4cc0e8fc@news01> (raw)
In-Reply-To: <e17dc37a0905040858t4886eb8bu53a297dc90f3eafe@mail.gmail.com>
On Mon, 4 May 2009 12:58:10 -0300
Murilo Opsfelder Araújo <mopsfelder@gmail.com> wrote:
> ./configure:#define TGETENT_ACCEPTS_NULL 1
>
> I think these are the options zsh was installed on server. If you need
> the options zsh port was compiled, it will take me more time. I have
> no root acces on the server.
OK, that's what I expected; it means zsh isn't responsible for buffer
allocation (or doesn't think it is, and if it got it wrong the system would
crash immediately, so it must be right).
> >> On the server side (where zsh crashes) there is no command 'infocmp'.
> >> The server is running FreeBSD.
> >
> > So this appears to be something to do with the response of FreeBSD to
> > being given a TERM setting of "linux"; can you reproduce this by setting
> > TERM to linux locally on the server?
>
> I set TERM to 'linux' on the server before calling 'zsh'. All seems
> ok. May be a problem with ssh connection.
I'm completely stuck now, I'm afraid: something obscure is happening down
in a library on a type of system I don't have access to.
--
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
next prev parent reply other threads:[~2009-05-05 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 12:35 Murilo Opsfelder Araújo
2009-04-30 13:54 ` Peter Stephenson
2009-04-30 21:22 ` Murilo Opsfelder Araújo
2009-05-01 9:18 ` Peter Stephenson
2009-05-04 15:58 ` Murilo Opsfelder Araújo
2009-05-05 15:36 ` Peter Stephenson [this message]
2009-05-05 15:40 ` Clint Adams
2009-05-05 15:48 ` 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=20090505163620.4cc0e8fc@news01 \
--to=pws@csr.com \
--cc=mopsfelder@gmail.com \
--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).