From: npostavs@users.sourceforge.net
To: "ISHIKAWA\,chiaki" <ishikawa@yk.rim.or.jp>
Cc: 26573@debbugs.gnu.org
Subject: bug#26573: 25.1; emacs 25.1 crashes while I am killing a bunch of lines
Date: Sat, 24 Jun 2017 18:45:18 -0400 [thread overview]
Message-ID: <87lgohovi9.fsf@users.sourceforge.net> (raw)
In-Reply-To: <3e4ebfef-16e4-4a7e-d591-557029c480c3@yk.rim.or.jp> (chiaki ISHIKAWA's message of "Sun, 25 Jun 2017 07:12:20 +0900")
"ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp> writes:
> Yes, it is too bad that emacs has become a little unstable.
> Maybe the distributed souce code management system may have something
> to do with it. Before, developers were very careful and use only a
> single master repository thus messing it up would have been a cardinal
> sin, but
> nowadays, people can create various branches and merge them (at least
> so that it builds/compiles). BUT, the runtime behavior may suffer.
> Just my guess.
These problems with the allocater have actually been triggered by a
glibc change. The malloc hooks were dropped which forces Emacs to use a
different configuration that had not been widely tested for a long time,
so meanwhile bugs had crept in.
next prev parent reply other threads:[~2017-06-24 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 2:57 bug#26573: 25.1; emacs 25.1 crashes while I am killing a bunch of lines ISHIKAWA,chiaki
2017-04-20 3:10 ` npostavs
2017-04-20 4:38 ` ISHIKAWA,chiaki
2017-04-20 8:16 ` ishikawa
2017-04-20 10:31 ` Tino Calancha
2017-04-20 14:04 ` ISHIKAWA,chiaki
2017-04-20 15:00 ` Eli Zaretskii
2017-06-24 21:52 ` npostavs
2017-06-24 22:12 ` ISHIKAWA,chiaki
2017-06-24 22:45 ` npostavs [this message]
2017-06-25 4:26 ` ISHIKAWA,chiaki
2017-06-25 12:07 ` npostavs
2017-04-20 15:01 ` Eli Zaretskii
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=87lgohovi9.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=26573@debbugs.gnu.org \
--cc=ishikawa@yk.rim.or.jp \
/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.