From: Elad Lahav <elahav@blackberry.com>
To: "eggert@cs.ucla.edu" <eggert@cs.ucla.edu>
Cc: "Emacs-devel@gnu.org" <Emacs-devel@gnu.org>
Subject: Re: Emacs on QNX
Date: Thu, 9 Nov 2017 17:17:43 +0000 [thread overview]
Message-ID: <1510247863.20595.19.camel@blackberry.com> (raw)
In-Reply-To: <4efa84fc-de6a-74dd-b2a7-71b4a536b5da@cs.ucla.edu>
On Wed, 2017-10-25 at 20:52 -0700, Paul Eggert wrote:
> I don't recall seeing it, no. Although this shouldn't prevent
> building on QNX,
> it does suggest a problem in the QNX implementation, which you should
> probably
> look into.
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.
I can work around the problem by increasing the stack size of the main
thread, but it would be nice to understand the increase in stack usage.
--Elad
next prev parent reply other threads:[~2017-11-09 17:17 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 [this message]
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
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
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=1510247863.20595.19.camel@blackberry.com \
--to=elahav@blackberry.com \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).