From: "ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp>
To: npostavs@users.sourceforge.net
Cc: 26573@debbugs.gnu.org
Subject: bug#26573: 25.1; emacs 25.1 crashes while I am killing a bunch of lines
Date: Sun, 25 Jun 2017 13:26:58 +0900 [thread overview]
Message-ID: <5e29d038-55ae-abfa-4fb1-1f9bf77bc0fc@yk.rim.or.jp> (raw)
In-Reply-To: <87lgohovi9.fsf@users.sourceforge.net>
On 2017/06/25 7:45, npostavs@users.sourceforge.net wrote:
> "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.
>
So a different reason. I came to my pet conclusion too fast.
I suspect that "configure" is a very difficult code to write correctly.
Again, thank you for your e-mails.
Emacs has been maintained in good condition by people like you.
So thank you very much!
Chiaki
next prev parent reply other threads:[~2017-06-25 4:26 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
2017-06-25 4:26 ` ISHIKAWA,chiaki [this message]
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
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=5e29d038-55ae-abfa-4fb1-1f9bf77bc0fc@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--cc=26573@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).