From: Bart Schaefer <schaefer@brasslantern.com>
To: "Wischnowsky, Sven" <Sven.Wischnowsky@t-systems.de>,
zsh-workers@sunsite.dk
Subject: Re: [bug report] 4.0.2 / 4.0.4 dumps core
Date: Thu, 22 Nov 2001 17:56:43 +0000 [thread overview]
Message-ID: <1011122175643.ZM3680@candle.brasslantern.com> (raw)
In-Reply-To: <7D865FB0D0A1D5118B6E000347055BBB14848B@G9JNT.mgb01.telekom.de>
On Nov 22, 9:09am, Wischnowsky, Sven wrote:
}
} Bart wrote:
}
} > I'm wondering if it wouldn't be more appropriate to duplicate the
} > strings in compctl.c:dumphashtable()
}
} Yes, I thought about doing that, too, and I don't really care where
} we put that ztrdup().
It's a matter of the principle that code that's only examining the
contents of a data structure shouldn't be changing those contents, even
if it restores them afterwards.
} > rather than simply allowing the completion code to poke bytes into
} > the real reswdtab.
}
} But it isn't the completion code. At least not for me. It SEGVed in
} the pattern matching code (called from the completion code).
Yes, but it's the completion code that's "violating" the pattern match
code API, in the sense that the pattern match code is supposed to get
writable strings and the completion code isn't providing them.
} And I was tempted to change that code to at least test if it was
} trying to write a '\0' onto the Null-byte at the end of a string.
That would unnecessarily penalize every other caller of the pattern
match code, wouldn't it?
If there's no problem with using dupstring() in dumphashtable(), then
I'd prefer to commit my patch rather than yours.
--
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
next prev parent reply other threads:[~2001-11-22 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 8:09 Wischnowsky, Sven
2001-11-22 17:56 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-23 8:13 Wischnowsky, Sven
2001-11-15 8:16 Wischnowsky, Sven
2001-11-21 18:35 ` Bart Schaefer
2001-11-14 9:03 Wischnowsky, Sven
2001-11-12 2:39 Akitoshi MORISHIMA
2001-11-12 9:10 ` 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=1011122175643.ZM3680@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=Sven.Wischnowsky@t-systems.de \
--cc=zsh-workers@sunsite.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).