all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: klaus.berndl@sdm.de, emacs-devel@gnu.org, storm@cua.dk
Subject: Re: repost: segfault on GNU/Linux
Date: Sat, 13 Mar 2004 21:56:04 -0500	[thread overview]
Message-ID: <E1B2LnI-0001A3-4F@fencepost.gnu.org> (raw)
In-Reply-To: <1078909835.7805.13.camel@coltrane.laudi.ka> (message from Jens Lautenbacher on Wed, 10 Mar 2004 10:10:35 +0100)

    Program received signal SIGSEGV, Segmentation fault.
    0x08203e7c in find_interval (tree=3D0x9fc13cc, position=3D1) at intervals.c=
    :652
    652         tree =3D balance_possible_root_interval (tree);
    (gdb) l

That pretty clearly suggests that the interval structure (text
properties) contains invalid data.  That is very strange, since the
previous but seems to concern overlays.  Overlays and text properties are
different data and are handled by different code.

Can you come up with a single reproducible case that always fails
in the same way?

    Fails only with CVS Emacs, Emacs 21.3 works.

This means we can't expect the bug to disappear automatically
with the next release.

						 XEmacs can't be tested,

Even if it could be tested, the results would not teach us anything
about this bug.  XEmacs does not have either intervals or overlays.

All my experience suggests that the approach of trying various cases
to look for a pattern of where failures occur is not useful, because
it generally does not lead anywhere.

The only way to find such bugs is by studying the code in detail,
finding what's invalid in the data, and tracing the causality back
step by step.

      reply	other threads:[~2004-03-14  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 23:35 repost: segfault on linux Jens Lautenbacher
2004-03-08 17:34 ` Kim F. Storm
2004-03-10  9:10   ` Jens Lautenbacher
2004-03-14  2:56     ` Richard Stallman [this message]

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=E1B2LnI-0001A3-4F@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=klaus.berndl@sdm.de \
    --cc=storm@cua.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.