From: Ken Olum <kdo@cosmos.phy.tufts.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16433@debbugs.gnu.org
Subject: bug#16433: Test case for newline cache corruption
Date: Mon, 26 May 2014 11:29:22 -0400 [thread overview]
Message-ID: <q528upo36el.fsf@cosmos.phy.tufts.edu> (raw)
In-Reply-To: <834n0flh3x.fsf@gnu.org> (message from Eli Zaretskii on Sat, 24 May 2014 11:24:02 +0300)
From: Eli Zaretskii <eliz@gnu.org>
Date: Sat, 24 May 2014 11:24:02 +0300
What are your locale settings?
LC_ALL=C
Also, is your build optimized or not? More generally, what are the
values of system-configuration and system-configuration-options in the
build where you reproduce this? If your build options are different
from mine, especially the optimization switches, perhaps that is part
of the issue somehow.
All I did was to download the trunk distribution and say "make".
system-configuration is "x86_64-unknown-linux-gnu"
system-configuration-options is ""
I'm running Ubuntu 12.04 LTS.
To avoid any possible dependence on window system issues, I tried
"emacs -nw" and got the same failure.
I'm happy to try to debug the C code if needed. I can use GDB.
Ken
next prev parent reply other threads:[~2014-05-26 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 19:37 bug#16433: 24.3.50; find_newline screws up in Rmail buffers Richard Stallman
2014-01-13 20:31 ` Eli Zaretskii
2014-01-14 17:06 ` Richard Stallman
2014-01-14 17:36 ` Eli Zaretskii
2014-01-15 12:29 ` Richard Stallman
2014-01-15 15:52 ` Eli Zaretskii
2014-05-22 20:38 ` bug#16433: Test case for newline cache corruption Ken Olum
2014-05-23 5:50 ` Eli Zaretskii
2014-05-24 8:24 ` Eli Zaretskii
2014-05-26 15:29 ` Ken Olum [this message]
2014-05-26 19:28 ` Eli Zaretskii
2014-05-27 15:14 ` Ken Olum
2014-05-27 16:20 ` Ken Olum
2014-05-27 18:04 ` Eli Zaretskii
2014-05-31 10:13 ` Eli Zaretskii
2014-05-31 18:27 ` Eli Zaretskii
2014-06-01 22:30 ` Ken Olum
2014-06-02 2:44 ` Eli Zaretskii
2014-06-05 16:57 ` Ken Olum
2014-06-05 17:31 ` Eli Zaretskii
2014-06-06 15:07 ` Richard Stallman
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=q528upo36el.fsf@cosmos.phy.tufts.edu \
--to=kdo@cosmos.phy.tufts.edu \
--cc=16433@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.