zsh-workers
 help / color / mirror / code / Atom feed
From: koen van hoof <koen.van_hoof@alcatel.be>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: TERMCAP problem.
Date: Tue, 16 Jan 2001 09:30:56 +0100	[thread overview]
Message-ID: <3A6406C0.AF8A744A@alcatel.be> (raw)
In-Reply-To: <1010115172300.ZM15781@candle.brasslantern.com>

[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]

Bart Schaefer wrote:

> On Jan 15,  9:46am, Dan Nelson wrote:
> } Subject: Re: TERMCAP problem.
> }
> } In the last episode (Jan 15), koen van hoof said:
> } > zsh V3.1.9 and termcap V1.3 on SunOS se9ws265 5.6 Generic_105181-03
> } > sun4u sparc
> [...]
> } > it core dumps, because at a certain moment getenv("TERM")
> } > returns 0 and this is fed into a strcmp.
> }
> } getenv("TERM") should never return 0.  screen sets both TERM and
> } TERMCAP on all my machines.
>
> But zsh shouldn't dump core when TERM is not set, even so.
>
> Koen, you're going to have to give us more details (if you can) about the
> core dump.  As far as I can tell, zsh never feeds the result of getenv()
> directly to strcmp().  $TERM is handled by params.c:termsetfn(), which
> always sets the global char *term to the empty string when $TERM is NULL;
> later comparisons on the terminal type always use *term, which should
> never be NULL unless ztrdup("") failed (which would indicate a serious
> memory allocation problem).
>

Bart,
Here is the backtrace.  If you want, I can also send you the core file.
#0  0xef5a4274 in strcmp () from /usr/lib/libc.so.1
#1  0x126c00 in tgetent (bp=0x0, name=0x15c2e8 "xterm") at termcap.c:469
#2  0x48608 in init_term () at init.c:478
#3  0x6f808 in termsetfn (pm=0x145e20, x=0x15c2e8 "xterm") at params.c:2763
#4  0x6c514 in setstrvalue (v=0xefffed28, val=0x15c2e8 "xterm") at params.c:1513

#5  0x6d7d0 in setsparam (s=0xeffffe45 "", val=0x15c2e8 "xterm") at
params.c:1810
#6  0x6767c in createparamtable () at params.c:515
#7  0x491d0 in setupvals () at init.c:715
#8  0x12158 in main (argc=1, argv=0xeffff4ac) at ./main.c:78

>
> --
> Bart Schaefer                                 Brass Lantern Enterprises
> http://www.well.com/user/barts              http://www.brasslantern.com
>
> Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net

--
==========================================================
Koen Van Hoof    koen.van_hoof@alcatel.be   32 3 451 60 31
==========================================================



[-- Attachment #2: Card for koen van hoof --]
[-- Type: text/x-vcard, Size: 156 bytes --]

begin:vcard 
n:Van Hoof;Koen
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:koen.van_hoof@alcatel.be
x-mozilla-cpt:;0
fn:Koen Van Hoof
end:vcard

  reply	other threads:[~2001-01-16  8:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 10:14 koen van hoof
2001-01-15 15:46 ` Dan Nelson
2001-01-15 17:23   ` Bart Schaefer
2001-01-16  8:30     ` koen van hoof [this message]
2001-01-16  8:52       ` Andrej Borsenkow
2001-01-16 10:42         ` koen van hoof
2001-01-16 10:54           ` Peter Stephenson
2001-01-16 11:19             ` Andrej Borsenkow
2001-01-16 11:56               ` koen van hoof
2001-01-16 12:11                 ` Andrej Borsenkow
2001-01-16 16:27                   ` koen van hoof
2001-01-16 17:05                     ` Peter Stephenson
2001-01-17  7:46                       ` koen van hoof
2001-01-17  7:53                       ` Andrej Borsenkow
2001-01-17 18:41                         ` Some general problems with exporting cariables (Was: TERMCAP problem. ) Andrej Borsenkow
2001-01-18 12:34                           ` koen van hoof
2001-01-18 13:16                             ` Andrej Borsenkow
2001-01-18 15:54                               ` koen van hoof
2001-01-19 15:05                                 ` Andrej Borsenkow

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=3A6406C0.AF8A744A@alcatel.be \
    --to=koen.van_hoof@alcatel.be \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.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).