From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24764@debbugs.gnu.org
Subject: bug#24764: 25.1.50; Another crash in automatic gc
Date: Sun, 23 Oct 2016 11:06:36 +0200 [thread overview]
Message-ID: <87insjjuxv.fsf@web.de> (raw)
In-Reply-To: <83oa2cp6yi.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Oct 2016 21:35:49 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> When did all those crashes started to happen?
I think they started ~ 1 week ago.
That would correlate with when I had rebuild Emacs. Before, I had
rebuild Emacs the last time 4 weeks ago (from emacs-25). Then, one week
ago, I pulled from emacs-25 and rebuilt Emacs. It could be that the
crashes started exactly then. It could be that an upgrade of some
library in my system I performed between 4 and 1 week ago could be
relevant. But these are quite a lot in Debian testing.
FWIW, another nasty bug appeared also ~ 1 week ago, maybe this is not
just coincidence: apparently, whenever Emacs downloads something from
the net, there is a chance of ~ one third that instead of the expected
contents, it gets something different: when I browse pages with eww,
often, instead of the page I expect, eww seems to show a part of the
contents of a different buffer. But this is not limited to eww: also
when I upgrade packages with `list-packages', Emacs often says that it
can't untar the contents, prompts me to select an encoding, etc. I
don't have problems with browsing online contents outside of Emacs.
> I think you had better used an older Emacs to run GDB, to avoid losing
> debugging sessions before we make the most use of them.
Ok, then I'll just use the emacs25 package that can now be installed
from Debian unstable for that.
Michael.
next prev parent reply other threads:[~2016-10-23 9:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 9:38 bug#24764: 25.1.50; Another crash in automatic gc Michael Heerdegen
2016-10-22 10:05 ` Eli Zaretskii
2016-10-22 11:41 ` Andreas Schwab
2016-10-22 12:01 ` Eli Zaretskii
2016-10-22 12:21 ` Eli Zaretskii
2016-10-22 14:05 ` Michael Heerdegen
2016-10-22 14:10 ` Eli Zaretskii
2016-10-22 14:43 ` Michael Heerdegen
2016-10-22 15:08 ` Eli Zaretskii
2016-10-22 18:25 ` Michael Heerdegen
2016-10-22 18:35 ` Eli Zaretskii
2016-10-23 9:06 ` Michael Heerdegen [this message]
2016-10-23 9:32 ` Eli Zaretskii
2016-10-23 10:22 ` Eli Zaretskii
2016-10-23 10:53 ` Michael Heerdegen
2016-10-23 12:06 ` Eli Zaretskii
2016-10-23 10:49 ` Michael Heerdegen
2016-10-23 10:24 ` Eli Zaretskii
2016-10-23 11:00 ` Michael Heerdegen
2016-10-23 12:08 ` Eli Zaretskii
2016-10-23 13:57 ` Eli Zaretskii
2016-10-23 15:53 ` Michael Heerdegen
2016-10-23 16:37 ` Michael Heerdegen
2016-10-23 17:01 ` Eli Zaretskii
2016-10-25 14:37 ` Michael Heerdegen
2016-10-25 16:46 ` Eli Zaretskii
2016-10-25 17:21 ` Michael Heerdegen
2016-10-25 18:17 ` Eli Zaretskii
2016-10-27 16:40 ` Michael Heerdegen
2016-10-27 17:18 ` Eli Zaretskii
2016-11-07 3:38 ` Eli Zaretskii
2016-11-07 11:36 ` Michael Heerdegen
2016-10-22 12:36 ` Eli Zaretskii
2016-10-22 13:54 ` Michael Heerdegen
2016-10-22 14:12 ` Michael Heerdegen
2016-10-22 14:24 ` Eli Zaretskii
2016-10-22 14:13 ` Eli Zaretskii
2016-10-23 9:32 ` Michael Heerdegen
2016-10-22 14:37 ` npostavs
2016-10-22 14:38 ` Eli Zaretskii
2016-10-22 14:51 ` Michael Heerdegen
2016-10-22 15:25 ` Eli Zaretskii
2016-10-22 15:33 ` 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=87insjjuxv.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=24764@debbugs.gnu.org \
--cc=eliz@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 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.