unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: xassert in dispextern.h
Date: Tue, 01 Mar 2005 20:41:47 +0100	[thread overview]
Message-ID: <x5ll97kvb8.fsf@lola.goethe.zz> (raw)
In-Reply-To: <uk6or5h2k.fsf@jasonrumney.net> (Jason Rumney's message of "Tue, 01 Mar 2005 18:58:27 +0000")

Jason Rumney <jasonr@gnu.org> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> That's completely backwards.
>
> What's completely backwards is to turn off a feature that helps us
> find bugs so that people can treat the CVS HEAD as a stable release
> of Emacs.

It does not help us find bugs.  That's the problem.  It's been on for
a month now, and the only bugs that were triggered by it were of the
sort that can much easier be found, reproduced and described when the
code does not abort.  I have wasted about 4 days of debugging on
something that turned out not be really a bug (in the sense that it
could lead to data destruction) but a quirk; and if the assertion had
not been turned on, both the severity and kind of this quirk would
have been _much_ better accessible for estimation.

GLYPH_DEBUG is not on by default either.  It is good to have the
assertions for tracking down a particular problem.  But I have seen no
evidence whatsoever that switching the default has helped us finding
even a single bug.

In contrast, it has kept me for several days from fixing real bugs and
making a release with other software.

And it also means that we have to tell people "don't use CVS Emacs, it
is slow and will crash".  And that means that all those people won't
help in finding _real-life_ bugs occuring in serious daily
application.  We don't have a formal beta program.  Getting this
feedback is necessary for ensuring a good quality release.

Feel free to volunteer any differing information if you have it
available.  If you know of any problem in the last 4 weeks that has
been discovered and fixed due to the changed default, I'd be glad to
hear of it.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-01 19:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 16:47 xassert in dispextern.h David Kastrup
2005-03-01 17:08 ` David Kastrup
2005-03-01 18:58   ` Jason Rumney
2005-03-01 19:41     ` David Kastrup [this message]
2005-03-01 21:32       ` Kim F. Storm
2005-03-01 21:51         ` David Kastrup
2005-03-01 22:50           ` Miles Bader
2005-03-01 23:14             ` Kim F. Storm
2005-03-02  0:52               ` David Kastrup
2005-03-03  2:29               ` Richard Stallman
2005-03-01 23:17             ` Luc Teirlinck
2005-03-02  0:35               ` Miles Bader
2005-03-02  1:01                 ` David Kastrup
2005-03-02  1:17                   ` Miles Bader
2005-03-02  1:38                     ` David Kastrup
2005-03-02  9:13                 ` Kim F. Storm
2005-03-02  9:47                   ` Miles Bader
2005-03-02 11:42                     ` Kim F. Storm
2005-03-02 12:21                     ` Andreas Schwab
2005-03-01 21:16     ` Kim F. Storm
2005-03-01 22:02       ` David Kastrup
2005-03-01 17:13 ` David Kastrup

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=x5ll97kvb8.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).