From: Scott Schwartz <schwartz@finch.cse.psu.edu>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: 9term bug
Date: Tue, 28 Oct 1997 01:32:35 -0500 [thread overview]
Message-ID: <19971028063235.21502.qmail@finch.cse.psu.edu> (raw)
Hi all,
I don't recall if this has been reported or not, but libtext from fails
to initialize everything in a newly allocated Text. (bcheck is your
friend.)
===================================================================
RCS file: RCS/text.c,v
retrieving revision 1.1
diff -c -r1.1 text.c
*** /tmp/T0a005Fs Tue Oct 28 01:30:37 1997
--- text.c Tue Oct 28 01:23:56 1997
***************
*** 47,52 ****
--- 47,53 ----
berror("textalloc: calloc");
t->length = 0;
t->base = 0;
+ t->end = 0;
t->p0 = 0;
t->p1 = 0;
t->pout = 0;
next reply other threads:[~1997-10-28 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-28 6:32 Scott Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-31 15:53 Bengt Kleberg
1997-11-01 0:47 ` James Matthew Farrow
1994-12-02 0:09 plexus-sys!mdash
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=19971028063235.21502.qmail@finch.cse.psu.edu \
--to=schwartz@finch.cse.psu.edu \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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.
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).