all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: schwab@suse.de, 26961-done@debbugs.gnu.org
Subject: bug#26961: 26.0.50; Possible timming issue in regex-tests.el
Date: Sat, 20 May 2017 14:54:32 +0300	[thread overview]
Message-ID: <83a867pwuf.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1705202017030.14366@calancha-pc> (message from Tino Calancha on Sat, 20 May 2017 20:20:39 +0900 (JST))

> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Sat, 20 May 2017 20:20:39 +0900 (JST)
> cc: Tino Calancha <tino.calancha@gmail.com>, 26961@debbugs.gnu.org, 
>     schwab@suse.de
> 
> On Sat, 20 May 2017, Eli Zaretskii wrote:
> 
> > Does the problem go away if you replace each AUTO_STRING in
> > load_warn_unescaped_character_literals with build_string?  IOW,
> > instead of this:
> >
> >  AUTO_STRING (separator, ", ");
> >
> > use this:
> >
> >  Lisp_Object separator = build_string (", ");
> >
> > and similarly for all the other strings used in the CALLN call in
> > load_warn_unescaped_character_literals.
> Yes, that change fixes the problem.  No crashes anymore.

Thanks, I installed such a change.





      reply	other threads:[~2017-05-20 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 10:19 bug#26961: 26.0.50; Possible timming issue in regex-tests.el Tino Calancha
2017-05-17 13:55 ` Tino Calancha
2017-05-17 16:32   ` Eli Zaretskii
2017-05-18  7:00     ` Tino Calancha
2017-05-18  7:50       ` Andreas Schwab
2017-05-18 15:04       ` Eli Zaretskii
2017-05-19  3:31         ` Tino Calancha
2017-05-19  7:14           ` Eli Zaretskii
2017-05-19 11:38             ` Tino Calancha
2017-05-20 10:04               ` Eli Zaretskii
2017-05-20 11:20                 ` Tino Calancha
2017-05-20 11:54                   ` Eli Zaretskii [this message]

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=83a867pwuf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26961-done@debbugs.gnu.org \
    --cc=schwab@suse.de \
    --cc=tino.calancha@gmail.com \
    /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.