zsh-workers
 help / color / mirror / code / Atom feed
From: Geoff Wing <gwing@primenet.com.au>
To: hniksic@srce.hr (Hrvoje Niksic)
Cc: zsh-workers@math.gatech.edu (zsh-workers)
Subject: Re: Purified zsh-3.0.1
Date: Sun, 10 Nov 1996 16:52:25 +1100 (EST)	[thread overview]
Message-ID: <199611100552.QAA03910@coral.primenet.com.au> (raw)
In-Reply-To: <kigd8xmttg1.fsf@jagor.srce.hr> from "Hrvoje Niksic" at Nov 10, 96 06:22:54 am

Hrvoje Niksic wrote:
:Geoff Wing (gwing@primenet.com.au) wrote:
:> :I hope this will help debugging...  Those ABR-s in line editor could
:> :be the cause of coredumps seen on Ultrix, that are quite hard to
:> :repeat.
:> This is a patch (on top of 2351 and its predecessor though it'll
:Yup, that fixes it (at least I cannot repeat it anymore).  Anyway, zsh
:is very stable, in the sense of purify.  Now there are no more
:array-bound reads or writes.
:> It doesn't seem likely to me that it would be the cause of any
:> coredumps.
:But it is possible, as soon as you read memory outside of the
:allocated block, isn't it?  The fact that the read was off-by-one
:could account for those dumps being hard to repeat.

Yes, though very unlikely. I don't know how your malloc stuff aligns things,
but the buffers involved are normally 81 bytes (for an 80 column screen)
and if accessing the 82nd byte places it outside a page boundary, then
that would be strange.

I think the most likely way for you to get it to reoccur, is by having 
delete/insert happen on a line, so scroll between lines which have
lots of similarities.
I play around a bit with a segment of my news file  `active' - 20k to 80k
worth.  Then do something like
% echo $(< active)<TAB>
and CTRL-A / CTRL-E combinations and other cursor movements.

Don't use the full `active' file: 800-900k, expand it on line, then press
return.  I had it going for over twenty minutes, memory use up to 27 meg,
before I got sick of it and killed it EXTERNALLY (no internal interrupt).
Not that many people are going to be doing this sort of thing, but...
The spelling correction stuff could use a bit of improvement -
I assume it rereads the directory for every single word on line.
-- 
Geoff Wing [gwing@primenet.com.au]   Technical Manager
  Phone    : +61-3-9818 2977	     PrimeNet - Internet Consultancy
  Facsimile: +61-3-9819 3788	     Web : <URL:http://www.primenet.com.au/>
  Mobile   : 0412 162 441


  reply	other threads:[~1996-11-10  5:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-10  4:25 Hrvoje Niksic
1996-11-10  5:12 ` Geoff Wing
1996-11-10  5:22   ` Hrvoje Niksic
1996-11-10  5:52     ` Geoff Wing [this message]
1996-11-11  1:01 ` Zoltan Hidvegi
1996-11-11  1:27   ` Hrvoje Niksic

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=199611100552.QAA03910@coral.primenet.com.au \
    --to=gwing@primenet.com.au \
    --cc=hniksic@srce.hr \
    --cc=zsh-workers@math.gatech.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.
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).