From: Jos Backus <Jos.Backus@nl.origin-it.com>
To: zsh-workers@sunsite.auc.dk
Subject: zsh-3.0.6 on BSD/OS
Date: Mon, 9 Aug 1999 12:25:57 +0200 [thread overview]
Message-ID: <19990809122557.B14467@hal.mpn.cp.philips.com> (raw)
Fyi:
1) On both BSD/OS 3.1 and 4.0.1, configure erroneously #defines
TGETENT_ACCEPTS_NULL, leading to a coredump later on in tgetstr() in
init.c:489:
Starting program: /home/jos/src/zsh-3.0.6/Src/zsh
Program received signal SIGSEGV, Segmentation fault.
0x280c8824 in cgetcap ()
(gdb) where
#0 0x280c8824 in cgetcap ()
#1 0x280c94b2 in cgetstr ()
#2 0x2809b899 in tgetstr ()
#3 0x8062194 in init_term ()
#4 0x806d485 in termsetfn ()
#5 0x806c34b in setstrvalue ()
#6 0x806c927 in setsparam ()
#7 0x806aa8a in createparamtable ()
#8 0x80626fd in setupvals ()
#9 0x80616c7 in main ()
#10 0x8049ff4 in __start ()
(gdb)
Undefining TGETENT_ACCEPTS_NULL in config.h fixes the problem.
2) On 4.0.1 (but not 3.1), I am seeing the following for every sourcefile:
gcc -c -I.. -I. -I. -DHAVE_CONFIG_H -Wall -Wno-implicit -Wmissing-prototypes -O2 builtin.c
In file included from system.h:58,
from zsh.h:59,
from builtin.c:30:
/usr/include/stdio.h:378: warning: no previous prototype for `__sputaux'
gcc is the system-supplied version 2.7.2.1 in both cases.
The shell built seems to work fine though.
Cheers,
--
Jos Backus _/ _/_/_/ "Reliability means never
_/ _/ _/ having to say you're sorry."
_/ _/_/_/ -- D. J. Bernstein
_/ _/ _/ _/
Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer;
next reply other threads:[~1999-08-09 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-09 10:25 Jos Backus [this message]
1999-08-09 14:34 ` Jos Backus
1999-08-09 17:36 ` Bart Schaefer
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=19990809122557.B14467@hal.mpn.cp.philips.com \
--to=jos.backus@nl.origin-it.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).