From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23912@debbugs.gnu.org, rms@gnu.org
Subject: bug#23912: 25.0.95; Abort in gc when working with streams
Date: Tue, 13 Sep 2016 17:58:48 +0200 [thread overview]
Message-ID: <87fup3aj0n.fsf@web.de> (raw)
In-Reply-To: <83k2ef982b.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Sep 2016 17:40:44 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> > I responded a few weeks ago, with what I thought I remembered, but I
> > seem to have been mistaken. Alas, I don't know any more now.
>
> I think I've succeeded in understanding this mystery: it's a left-over
> from an old GCPRO, which was replaced with an assertion to make sure
> GC never happens while this code runs. And since nowadays GCPRO is a
> no-op, we can remove this flag.
Ok, that's great, thank you very much...ehm, can you please make the
change on master then (if you didn't yet)?
TIA,
Michael.
next prev parent reply other threads:[~2016-09-13 15:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 16:48 bug#23912: 25.0.95; Abort in gc when working with streams Michael Heerdegen
2016-07-07 17:15 ` Eli Zaretskii
2016-07-07 17:38 ` Michael Heerdegen
2016-07-07 17:57 ` Dmitry Antipov
2016-07-07 20:34 ` Michael Heerdegen
2016-07-08 6:14 ` Eli Zaretskii
2016-07-12 21:53 ` Michael Heerdegen
2016-07-13 15:52 ` Michael Heerdegen
2016-07-13 20:19 ` Eli Zaretskii
2016-07-13 21:28 ` Michael Heerdegen
2016-07-13 20:16 ` Eli Zaretskii
2016-07-13 21:23 ` Michael Heerdegen
2016-07-14 14:58 ` Eli Zaretskii
2016-07-14 18:32 ` Michael Heerdegen
2016-07-23 16:16 ` Michael Heerdegen
2016-07-23 16:30 ` Eli Zaretskii
2016-09-12 20:18 ` Michael Heerdegen
2016-09-13 12:25 ` Richard Stallman
2016-09-13 14:40 ` Eli Zaretskii
2016-09-13 15:58 ` Michael Heerdegen [this message]
2016-09-14 17:42 ` Eli Zaretskii
2016-07-14 16:15 ` Adrián Medraño Calvo
2016-07-14 18:30 ` Michael Heerdegen
2016-07-14 18:49 ` Eli Zaretskii
2016-07-14 21:54 ` Michael Heerdegen
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=87fup3aj0n.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=23912@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@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).