From: Daniel Colascione <dancol@dancol.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 13759@debbugs.gnu.org
Subject: bug#13759: 24.3.50; bootstrap failed; bootstrap-emacs segfaults
Date: Tue, 19 Feb 2013 21:57:09 -0800 [thread overview]
Message-ID: <512465B5.5030207@dancol.org> (raw)
In-Reply-To: <51245B4B.6000803@dancol.org>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
On 2/19/2013 9:12 PM, Daniel Colascione wrote:
> I don't know why we suddenly started seeing this behavior.
Revision 111820, "Prefer `message1' over `message'.", caused us to start calling
message1 instead of message in sheap.c. message1 ends up calling message_dolog,
which tries to allocate a *Messages* buffer. Maybe Fdump_emacs should bind
Vmessage_max_log?
Anyway, I've installed the following patch to trunk, which fixes the problem. If
we want to go back to using message1, let's somehow make sure it doesn't log.
revno: 111830
committer: Daniel Colascione <dancol@dancol.org>
branch nick: cyg
timestamp: Tue 2013-02-19 21:43:53 -0800
message:
2013-02-19 Daniel Colascione <dancol@dancol.org>
* sheap.c (report_sheap_usage): Use message, not message1, so
that we don't try to create a buffer while we're in the middle
of dumping Emacs. Explain why.
diff:
=== modified file 'src/ChangeLog'
--- src/ChangeLog 2013-02-19 03:29:28 +0000
+++ src/ChangeLog 2013-02-20 05:43:53 +0000
@@ -1,3 +1,9 @@
+2013-02-19 Daniel Colascione <dancol@dancol.org>
+
+ * sheap.c (report_sheap_usage): Use message, not message1, so
+ that we don't try to create a buffer while we're in the middle
+ of dumping Emacs. Explain why.
+
2013-02-19 Eli Zaretskii <eliz@gnu.org>
* w32proc.c (new_child): Avoid leaking handles if the subprocess
=== modified file 'src/sheap.c'
--- src/sheap.c 2013-02-17 16:49:27 +0000
+++ src/sheap.c 2013-02-20 05:43:53 +0000
@@ -91,5 +91,8 @@
char buf[200];
sprintf (buf, "Static heap usage: %d of %d bytes",
bss_sbrk_ptr - bss_sbrk_buffer, STATIC_HEAP_SIZE);
- message1 (buf);
+ /* Don't change this call to message1! message1 can log
+ messages, and at this point, we're not allowed to create
+ buffers. */
+ message ("%s", buf);
}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2013-02-20 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 0:06 bug#13759: 24.3.50; bootstrap failed; bootstrap-emacs segfaults Katsumi Yamaoka
2013-02-20 5:12 ` Daniel Colascione
2013-02-20 5:57 ` Daniel Colascione [this message]
2013-02-20 10:19 ` Katsumi Yamaoka
2013-02-20 23:37 ` Katsumi Yamaoka
2013-02-21 2:39 ` Ken Brown
2013-02-21 5:01 ` Katsumi Yamaoka
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=512465B5.5030207@dancol.org \
--to=dancol@dancol.org \
--cc=13759@debbugs.gnu.org \
--cc=yamaoka@jpl.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.