From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23912@debbugs.gnu.org
Subject: bug#23912: 25.0.95; Abort in gc when working with streams
Date: Sat, 23 Jul 2016 18:16:36 +0200 [thread overview]
Message-ID: <87y44sqqhn.fsf@web.de> (raw)
In-Reply-To: <87furc6pg1.fsf@web.de> (Michael Heerdegen's message of "Thu, 14 Jul 2016 20:32:14 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> > Why do we want to prevent GC while working on Vprin1_to_string_buffer?
> > [...] What bad things could happen if we just remove it?
>
> FWIW, I've commented it out and recompiled. Let's see what happens.
The only thing that i noticed was that by issue was completely fixed.
What can we do now with this bug report?
Thanks,
Michael.
next prev parent reply other threads:[~2016-07-23 16:16 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y44sqqhn.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=23912@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.