From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15861@debbugs.gnu.org
Subject: bug#15861: 24.3.50; lots of byte-compiler code written to *Messages* at runtime
Date: Thu, 14 Nov 2013 10:50:20 -0800 (PST) [thread overview]
Message-ID: <17283efd-8495-4d92-9e95-318f32da076a@default> (raw)
In-Reply-To: <<83eh6izw6w.fsf@gnu.org>>
> It's some snafu, but it's hard to say what is at work exactly. I
> tried to reproduce this, but couldn't, because some function this
> code calls is not defined. So I don't even know if compiling this
> in Emacs 24 would prevent the problem (but I guess you can check
> this yourself).
I have done that now, in this build:
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-11-12 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'
That made no difference. But see below.
> IOW, there's not enough information here to dig into the problem.
I took another look, and there is no bug; sorry.
FYI, I had some debug calls to `message' in the file, and one of
them printed the value of argument ORIG-FUN. Apparently the value
of that argument is what has changed in recent builds.
Printing that argument now leads to tons of binary code plus the
complete doc string being logged. IOW, the argument now seems
to be a byte-compiled function, whereas it was not compiled before.
Sorry for the noise. I will close the bug.
next parent reply other threads:[~2013-11-14 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<701df652-aa30-4607-97dc-d02075f9094c@default>
[not found] ` <<83eh6izw6w.fsf@gnu.org>
2013-11-14 18:50 ` Drew Adams [this message]
2013-11-14 23:01 ` bug#15861: 24.3.50; lots of byte-compiler code written to *Messages* at runtime Stefan Monnier
2013-11-11 19:30 Drew Adams
2013-11-12 8:15 ` Andreas Röhler
2013-11-12 17:38 ` Drew Adams
2013-11-12 18:10 ` Andreas Röhler
2013-11-14 18:15 ` Eli Zaretskii
2013-11-14 19:50 ` Stefan Monnier
2013-11-14 21:27 ` Drew Adams
2013-11-14 22:59 ` Stefan Monnier
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=17283efd-8495-4d92-9e95-318f32da076a@default \
--to=drew.adams@oracle.com \
--cc=15861@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.