all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 42931@debbugs.gnu.org, larsi@gnus.org, bruno@clisp.org,
	p.stephani2@gmail.com, psainty@rcon.net.nz
Subject: bug#42931: 27.1; json-pretty-print-buffer on ~2MB line causes core dump
Date: Tue, 25 Aug 2020 09:12:58 +0300	[thread overview]
Message-ID: <83k0xn5k45.fsf@gnu.org> (raw)
In-Reply-To: <14e2aff5-20e3-03a3-50ae-cfabee5bc406@cs.ucla.edu> (message from Paul Eggert on Mon, 24 Aug 2020 16:46:01 -0700)

> Cc: 42931@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
>  Eli Zaretskii <eliz@gnu.org>, Philipp Stephani <p.stephani2@gmail.com>,
>  Bruno Haible <bruno@clisp.org>
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 24 Aug 2020 16:46:01 -0700
> 
> In theory even O(log N) might not be good enough if Emacs has a tiny stack and a 
> huge buffer, but I doubt whether this is of practical concern.

What about "normal" Emacs builds?  They usually have between 2MB and
8MB of stack.  Should we worry about stack overflow in these cases?
Maybe it is worth to add a stack-overflow protection to diffseq.h
anyway?  Almost anything is better than a segfault.

Thanks.





  reply	other threads:[~2020-08-25  6:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 13:50 bug#42931: 27.1; json-pretty-print-buffer on ~2MB line causes core dump Phil Sainty
2020-08-19 14:15 ` Lars Ingebrigtsen
2020-08-19 15:18   ` Eli Zaretskii
2020-08-20 13:22     ` Lars Ingebrigtsen
2020-08-20 13:26       ` Philipp Stephani
2020-08-20 13:39       ` Eli Zaretskii
2020-08-24 23:46 ` Paul Eggert
2020-08-25  6:12   ` Eli Zaretskii [this message]
2020-08-25 18:19     ` Paul Eggert

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=83k0xn5k45.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42931@debbugs.gnu.org \
    --cc=bruno@clisp.org \
    --cc=eggert@cs.ucla.edu \
    --cc=larsi@gnus.org \
    --cc=p.stephani2@gmail.com \
    --cc=psainty@rcon.net.nz \
    /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.