unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Rob Browning <rlb@defaultvalue.org>
Cc: 21474@debbugs.gnu.org
Subject: bug#21474: emacs-25.0.50: compilation error in leim: Args out of
Date: Sat, 26 Nov 2016 17:30:46 -0500	[thread overview]
Message-ID: <CAM-tV-8zpcpVh151Jm3-xGymPY0F92sTTnNXF6FcBwL6Ga86iA@mail.gmail.com> (raw)
In-Reply-To: <87shqe0wmd.fsf@trouble.defaultvalue.org>

On Sat, Nov 26, 2016 at 4:17 PM, Rob Browning <rlb@defaultvalue.org> wrote:
>
> In any case, after poking around in the newer emacs-25 commits (as
> mentioned above), it seemed like applying these allocation related
> patches might help:
>
>   b6998ea * src/regex.h (re_match_object): Improve commentary.
>   ad66b3f Fix handling of allocation in regex matching
>   f6134bb Port to GCC 6.2.1 + --enable-gcc-warnings
>   c2a1792 * src/regex.c (re_search_2): Make new code safe for -Wjump-misses-init.
>   ee04aed Fix handling of buffer relocation in regex.c functions
>   7bb5c4f Port --enable-gcc-warnings to bleeding-edge glibc
>   1047496 Another fix for using pointer to buffer text
>   96ac0c3 Yet another fix for using pointers into buffer text
>   32827b3 Default REL_ALLOC to 'no'
>   fee4cef Revert fixes to allocation of regex matching
>   43986d1 Inhibit buffer relocation during regex searches
>   0221b7a Mark relocation workarounds with REL_ALLOC

You could probably trim a bit, e.g. just the "Default REL_ALLOC to
'no'" by itself should work, or a minimal set with REL_ALLOC=yes
should be listed at
https://lists.gnu.org/archive/html/emacs-devel/2016-10/msg00971.html.

>
> And indeed, with those, I've yet to see a crash, but as we know, they're
> intermittent.  To help increase confidence, two others who have been
> able to produce the crash are probably also going to test that tree
> soon.

Doing  'make extraclean && ./configure && make' seemed to be fairly
reliable way of reproducing it (if configured with GTK).





  reply	other threads:[~2016-11-26 22:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 12:40 bug#21474: emacs-25.0.50: compilation error in leim: Args out of range Thomas Klausner
2015-09-14 12:47 ` Eli Zaretskii
2015-09-14 15:58   ` Thomas Klausner
2015-09-14 17:39     ` Eli Zaretskii
2015-09-19 19:59       ` Thomas Klausner
2016-11-25 22:23 ` bug#21474: emacs-25.0.50: compilation error in leim: Args out of Rob Browning
2016-11-25 22:34   ` Noam Postavsky
2016-11-26  7:02     ` Eli Zaretskii
2016-11-26 21:17       ` Rob Browning
2016-11-26 22:30         ` Noam Postavsky [this message]
2016-11-26 23:15           ` Rob Browning
2016-11-27  2:53             ` Noam Postavsky
2016-11-27  3:16               ` Rob Browning
2016-11-27 13:53                 ` Noam Postavsky
     [not found] <87a8cn2oek.fsf@trouble.defaultvalue.org>
2016-11-25 22:45 ` Rob Browning
2016-11-26  7:12   ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM-tV-8zpcpVh151Jm3-xGymPY0F92sTTnNXF6FcBwL6Ga86iA@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=21474@debbugs.gnu.org \
    --cc=rlb@defaultvalue.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).