all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: schwab@suse.de, rhymer123@gmail.com, npostavs@gmail.com,
	22149@debbugs.gnu.org
Subject: bug#22149: 24.4; gdb stack overflow in regexp matcher
Date: Sat, 14 Mar 2020 12:14:24 +0200	[thread overview]
Message-ID: <838sk3ckfz.fsf@gnu.org> (raw)
In-Reply-To: <22A4D20C-E8EE-4C88-A3D9-6412D3C126B3@acm.org> (message from Mattias Engdegård on Sat, 14 Mar 2020 10:04:38 +0100)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sat, 14 Mar 2020 10:04:38 +0100
> Cc: Noam Postavsky <npostavs@gmail.com>, 22149-done@debbugs.gnu.org,
>         Andreas Schwab <schwab@suse.de>, Cheng-An Yang <rhymer123@gmail.com>
> 
> 14 mars 2020 kl. 08.58 skrev Eli Zaretskii <eliz@gnu.org>:
> 
> >  Moreover, we
> > might decide, for different reasons, to bump up the stack size of the
> > Emacs binary, which will indirectly fix this problem by making it less
> > probable.
> 
> I'm not sure how the C and regexp engine stacks relate to each other in practice -- main() attempts to grow the C stack to accommodate the maximal regexp stack, but SAFE_ALLOCA is set up to use the heap when necessary. Surely we could decouple them more or less entirely, since the extra cost for malloc is bound to be small when a lot of regexp stack is needed.

I think regex-emacs.c already overrides some of the SAFE_ALLOCA
machinery to that effect, does it not?





  reply	other threads:[~2020-03-14 10:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12  6:16 bug#22149: 24.4; gdb stack overflow in regexp matcher Cheng-An Yang
2015-12-12 10:13 ` Andreas Schwab
2016-07-01  3:16   ` npostavs
2020-03-13 18:58 ` Mattias Engdegård
2020-03-13 19:39   ` Eli Zaretskii
2020-03-13 20:11     ` Mattias Engdegård
2020-03-14  7:58       ` Eli Zaretskii
2020-03-14  9:04         ` Mattias Engdegård
2020-03-14 10:14           ` Eli Zaretskii [this message]
2020-03-14 10:43             ` Mattias Engdegård

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=838sk3ckfz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22149@debbugs.gnu.org \
    --cc=mattiase@acm.org \
    --cc=npostavs@gmail.com \
    --cc=rhymer123@gmail.com \
    --cc=schwab@suse.de \
    /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.