From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Elad Lahav <elahav@blackberry.com>
Cc: "eggert@cs.ucla.edu" <eggert@cs.ucla.edu>,
"Emacs-devel@gnu.org" <Emacs-devel@gnu.org>
Subject: Re: Emacs on QNX
Date: Thu, 9 Nov 2017 12:30:01 -0500 [thread overview]
Message-ID: <CAM-tV-9NcW5iP5E5oJmK=2mgJxBz140OvXT_e2eSxR71H+LgcQ@mail.gmail.com> (raw)
In-Reply-To: <1510247863.20595.19.camel@blackberry.com>
On Thu, Nov 9, 2017 at 12:17 PM, Elad Lahav <elahav@blackberry.com> wrote:
> I forgot to mention that I did investigate the problem. The recursion
> is not infinite, just very deep. In QNX all stack sizes are fixed,
> including that of the main thread. The default size for the main thread
> is 512K, but some elisp modules (e.g., verilog) require more in version
> 26 to compile. There is no such problem in the 25.x code. I wonder if
> the modules themselves have changed, or something else is causing more
> stack space to be used.
Could be [1: f0a1e9ec3f], which makes read1 try to use a
stack-allocated buffer instead of a heap-allocated one.
[1: f0a1e9ec3f]: 2016-12-08 13:00:32 -0800
Make read1 more reentrant
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=f0a1e9ec3fba3d5bea5bd62f525dba3fb005d1b1
next prev parent reply other threads:[~2017-11-09 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 22:13 Emacs on QNX Elad Lahav
2017-10-23 4:51 ` Paul Eggert
2017-10-23 11:27 ` Elad Lahav
2017-10-24 1:52 ` Elad Lahav
2017-10-24 20:14 ` Paul Eggert
2017-10-25 2:27 ` Elad Lahav
2017-10-26 3:52 ` Paul Eggert
2017-11-09 17:17 ` Elad Lahav
2017-11-09 17:23 ` Eli Zaretskii
2017-11-30 17:43 ` Elad Lahav
2017-11-30 23:41 ` Paul Eggert
2017-12-01 2:06 ` Elad Lahav
2017-12-01 3:37 ` Paul Eggert
2017-12-01 11:55 ` Elad Lahav
2017-12-11 0:25 ` Elad Lahav
2017-11-09 17:30 ` Noam Postavsky [this message]
2017-11-09 17:33 ` Elad Lahav
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='CAM-tV-9NcW5iP5E5oJmK=2mgJxBz140OvXT_e2eSxR71H+LgcQ@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=elahav@blackberry.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.