unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-devel@gnu.org
Subject: Re: In FOR-RELEASE
Date: Mon, 20 Jun 2005 15:08:33 +0200	[thread overview]
Message-ID: <v91x6xw4z2.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1DjLs0-0006F9-Id@fencepost.gnu.org> (Richard Stallman's message of "Fri, 17 Jun 2005 14:47:12 -0400")

On Fri, Jun 17 2005, Richard Stallman wrote:

> FOR-RELEASE mentiones these bugs:
>
>     ** Investigate reported crashes in compact_small_strings.
>
>     ** Investigate reported crashes related to using an
>     invalid pointer from string_free_list.
>
> They were reported a long time ago, before we realized it was a good
> idea to copy the actual bug reports there.  They have not been
> reported recently that I recall.  Does anyone recall seeing such
> bugs recently?
>
> Is there any reason to think they are fixed already?
>
> Could someone possibly search for these bug reports,
> see who reported them, etc?

I've submitted a bug report concerning compact_small_strings:

,----[ http://thread.gmane.org/gmane.emacs.pretest.bugs/3866 ]
| From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
| Subject: redisplay problem (compact_small_strings)
| To: emacs-pretest-bug@gnu.org
| Date: Mon, 13 Sep 2004 17:35:03 +0200
| Reply-To: Reiner Steib <Reiner.Steib@gmx.de>
| Message-ID: <v9d60qqj14.fsf@marauder.physik.uni-ulm.de>
`----

This problem was solved later, IIRC.  I didn't see this problem in the
last months.

A different one concerning compact_small_strings was:

,----[ http://thread.gmane.org/gmane.emacs.pretest.bugs/4371 ]
| From: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
| Newsgroups: gmane.emacs.pretest.bugs
| Subject: seg fault in compact_small_strings()
| Date: Fri, 29 Oct 2004 12:49:55 +0100
| To: emacs-pretest-bug@gnu.org
`----

Kim F. Storm sent a patch and Stephen Eglen posted a different
backtrace.

Some search results for compact_small_strings on emacs-devel are:

| From: Kim F. Storm <storm@cua.dk>
| Subject: Fix to long-standing crashes in GC
| To: emacs-devel@gnu.org
| Date: 2004-05-12 13:19:54 GMT
 
| From: Bob Halley <halley@play-bow.org>
| Subject: random core dumps
| To: emacs-devel@gnu.org
| Date: 2002-12-05 12:06:14 GMT
 
| From: Sam Steingold <sds@gnu.org>
| Subject: cvs head crash in GC
| To: emacs-devel@gnu.org
| Date: 2003-04-01 00:24:56 GMT
 
Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  reply	other threads:[~2005-06-20 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17 18:47 In FOR-RELEASE Richard Stallman
2005-06-20 13:08 ` Reiner Steib [this message]
2005-06-20 17:16   ` Stephen Eglen
2005-06-21  1:02     ` Miles Bader
2005-06-21  2:00   ` Richard Stallman

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=v91x6xw4z2.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).