From: Thomas Dickey <dickey@saltmine.radix.net>
Subject: Re: Crash in tparam.c on OpenBSD
Date: 2 Jan 2004 11:01:04 GMT [thread overview]
Message-ID: <bt3j1g$skb$1@news1.radix.net> (raw)
In-Reply-To: mailman.868.1073039641.868.bug-gnu-emacs@gnu.org
Eli Zaretskii <eliz@elta.co.il> wrote:
>> Date: Fri, 2 Jan 2004 00:54:31 +0200
>> From: Casper Gripenberg <casper.gripenberg@kotiportti.fi>
>>
>> (gdb) up
>> #4 0x123709 in tparam (string=0x49b105 "\e[3%p1%dm", outstring=0x0, len=0,
>> arg0=6, arg1=2496000, arg2=1, arg3=8) at tparam.c:105
>> (gdb) up
>> #5 0x4b3a9 in turn_on_face (f=0x261600, face_id=11) at term.c:2107
>> (gdb)
>>
>> Which looks like this:
>>
>> if (fg >= 0 && TS_set_foreground)
>> {
>> > p = tparam (TS_set_foreground, NULL, 0, (int) fg);
>> OUTPUT (p);
>> xfree (p);
>> }
>>
>> Where TS_set_foreground is the "\e[3%p1%dm" string.
>>
>> I have no idea what all this means
> It means that your Emacs was compiled for termcap, but the TERM entry
> it gets fed is for terminfo, which is a newer method of specifying
> terminal capabilities. Emacs as compiled on your machine cannot
> handle terminfo entries, so it barfs.
> There should be an entry in the PROBLEMS file named "Emacs aborts
> inside the function `tparam1'" which tells you more, including
> suggested ways to solve this problem.
This appears to be a problem with emacs' configure script. It shouldn't
have to compile-in most of the logic for tparam, since that can be done
with calls to the "real" tgoto.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
next prev parent reply other threads:[~2004-01-02 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 22:54 Crash in tparam.c on OpenBSD Casper Gripenberg
2004-01-02 9:25 ` Eli Zaretskii
2004-01-02 13:43 ` Casper Gripenberg
[not found] ` <mailman.868.1073039641.868.bug-gnu-emacs@gnu.org>
2004-01-02 11:01 ` Thomas Dickey [this message]
2004-01-03 11:48 ` Eli Zaretskii
[not found] ` <mailman.897.1073134721.868.bug-gnu-emacs@gnu.org>
2004-01-04 2:25 ` Thomas Dickey
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='bt3j1g$skb$1@news1.radix.net' \
--to=dickey@saltmine.radix.net \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).