From: ead@ixian.com
To: Roderick Schertler <roderick@gate.net>
Cc: <zsh-workers@math.gatech.edu>
Subject: Re: glob [a-z]## bug in beta18
Date: Thu, 23 May 1996 08:34:14 -0700 [thread overview]
Message-ID: <199605231534.AA26088@waltz.rahul.net> (raw)
Roderick,
Roderick Schertler <roderick@gate.net>:
] Zoltan Hidvegi <hzoli@cs.elte.hu>:
] >> j:1% print -l 'setopt extended_glob' 'print -c [a-z]#' | zsh-2.6-beta18 -f
] >> bug.1 ok
] >
] > I cannot reproduce this. What OS and which C compiler do you use?
]
] I should have realized that this bug was too severe to be universal.
] Sorry about that. I saw that behavior on dgux 5.4.3.10 with gcc 2.5.8
] (the standard system compiler). When I recompiled with debugging rather
] than optimization the problem disappeared, so by definition it must be a
] bug in the compiler.
I cannot speak to the problem at hand, and have not looked at the zsh
code in question, but ceteris paribus, this line of reasoning is faulty.
When a "problem disappears", that does not mean that another one,
elsewhere, doesn't move to take it's place. Example: heap corruption due
to bad pointer management with optimization on, but valid memory getting
trashed with optimization off/debugging on.
Eric De Mund <ead@ixian.com>
http://www.ixian.com/ixian/ead/
"It's harder to solve people's problems than it is to design really neat
products." --Stewart Alsop
next reply other threads:[~1996-05-23 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-23 15:34 ead [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-05-22 16:44 Roderick Schertler
1996-05-22 17:32 ` Zoltan Hidvegi
1996-05-23 14:47 ` Roderick Schertler
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=199605231534.AA26088@waltz.rahul.net \
--to=ead@ixian.com \
--cc=roderick@gate.net \
--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).