From: Bart Schaefer <schaefer@brasslantern.com>
To: Vincent Lefevre <vincent@vinc17.org>, zsh-users@sunsite.dk
Subject: Re: can't find termcap info
Date: Tue, 18 Sep 2001 16:17:08 -0700 [thread overview]
Message-ID: <010918161708.ZM8169@candle.brasslantern.com> (raw)
In-Reply-To: <20010919005025.A18079@greux.loria.fr>
On Sep 19, 12:50am, Vincent Lefevre wrote:
>
> (gdb) backtrace
> #0 chunk_alloc (ar_ptr=0x2abf1d60, nb=24) at malloc.c:2814
> #1 0x2ab5c5ce in __libc_malloc (bytes=16) at malloc.c:2696
> #2 0x2aae1f09 in _init () from /lib/libtermcap.so.2
> #3 0x2aae2328 in _init () from /lib/libtermcap.so.2
> #4 0x2aae2b3b in _init () from /lib/libtermcap.so.2
> #5 0x2aae2bc8 in tgetent () from /lib/libtermcap.so.2
As I feared, it's crashing in the termcap library itself; there's nothing
we can directly do about this.
> > If $HOME/.termcap isn't too huge, include that too.
>
> It's too huge: 748544 KB.
>
> I generated it with "tic -C -T terminfo.src"
Hrm. I'd be a bit suspicious of this; it's entirely possible that there
are termcap strings that the ncurses tgetent would accept but which the
(older) libtermcap tgetent would choke on.
Try either (a) copy /etc/termcap and append your nettle def'n to that,
or (b) edit down your ~/.termcap to contain just the rxvt and nettle
def'ns (and any that rxvt may depend on).
Either that, or you're going to have to "configure --with-curses-terminfo"
and rebuild zsh.
next prev parent reply other threads:[~2001-09-18 23:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 12:25 Vincent Lefevre
2001-09-18 12:38 ` Will Yardley
2001-09-18 12:59 ` Vincent Lefevre
2001-09-18 13:25 ` Will Yardley
2001-09-18 14:51 ` Vincent Lefevre
2001-09-18 15:53 ` a normal guy
2001-09-18 16:13 ` Vincent Lefevre
2001-09-18 16:28 ` a normal guy
2001-09-18 17:04 ` Vincent Lefevre
2001-09-18 19:19 ` Bart Schaefer
2001-09-18 20:39 ` Vincent Lefevre
2001-09-18 22:10 ` Bart Schaefer
2001-09-18 22:50 ` Vincent Lefevre
2001-09-18 23:17 ` Bart Schaefer [this message]
2001-09-19 10:10 ` Vincent Lefevre
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=010918161708.ZM8169@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=vincent@vinc17.org \
--cc=zsh-users@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).