From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 17753@debbugs.gnu.org, markus.hoenicka@mhoenicka.de
Subject: bug#17753: Cygwin emacs-X11 core dump
Date: Mon, 20 Oct 2014 18:29:09 +0300 [thread overview]
Message-ID: <83wq7ubvzu.fsf@gnu.org> (raw)
In-Reply-To: <5444F224.2060000@cornell.edu>
> Date: Mon, 20 Oct 2014 07:29:40 -0400
> From: Ken Brown <kbrown@cornell.edu>
> CC: Eli Zaretskii <eliz@gnu.org>, 17753@debbugs.gnu.org
>
> I'm not aware of any reason that increasing the stack size should make things
> worse.
There is one reason I could think of: the amount of stack memory
reserved for each thread. If the program whose PE header specifies a
8MB stack creates additional threads, by default each thread gets 8MB
of memory address space reserved for it (not allocated, just
reserved). I've looked in the Cygwin sources, and the way threads are
created there is like that.
This could potentially cause trouble in a memory starved system,
because it might run out of address space. This is, of course, highly
improbably on 64-bit systems, but can happen on 32-bit systems.
However, I don't think this is a serious danger, and we are talking
about 64-bit builds anyway.
next prev parent reply other threads:[~2014-10-20 15:29 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 21:55 bug#17753: Cygwin emacs-X11 core dump markus.hoenicka
2014-06-11 2:51 ` Eli Zaretskii
2014-06-11 6:16 ` Markus Hoenicka
2014-06-11 14:47 ` Eli Zaretskii
2014-06-13 22:53 ` markus.hoenicka
2014-06-11 12:28 ` Ken Brown
2014-06-11 15:03 ` Eli Zaretskii
2014-07-04 21:21 ` markus.hoenicka
2014-07-05 14:03 ` Ken Brown
2014-07-07 21:31 ` markus.hoenicka
2014-07-09 13:57 ` Ken Brown
2014-07-09 14:30 ` Markus Hoenicka
2014-09-17 9:45 ` Markus Hoenicka
2014-09-17 10:16 ` Eli Zaretskii
2014-09-17 10:52 ` Eli Zaretskii
2014-09-17 11:04 ` Markus Hoenicka
2014-09-17 15:17 ` Ken Brown
2014-09-17 17:06 ` Eli Zaretskii
2014-09-22 7:14 ` Markus Hoenicka
2014-09-22 13:32 ` Ken Brown
2014-09-22 14:04 ` Markus Hoenicka
2014-09-22 14:48 ` Eli Zaretskii
2014-10-07 7:02 ` Markus Hoenicka
2014-10-07 14:56 ` Ken Brown
2014-10-07 15:05 ` Eli Zaretskii
2014-10-07 16:05 ` Markus Hoenicka
2014-10-07 17:04 ` Eli Zaretskii
2014-10-07 20:48 ` Markus Hoenicka
2014-10-09 8:17 ` Markus Hoenicka
2014-10-09 8:56 ` Eli Zaretskii
2014-10-09 9:08 ` Markus Hoenicka
2014-10-09 10:35 ` Eli Zaretskii
2014-10-09 10:44 ` Markus Hoenicka
2014-10-09 11:22 ` Eli Zaretskii
2014-10-09 11:47 ` Markus Hoenicka
2014-10-09 11:55 ` Eli Zaretskii
2014-10-11 15:31 ` Ken Brown
2014-10-12 0:07 ` Markus Hoenicka
2014-10-20 10:59 ` Markus Hoenicka
2014-10-20 11:29 ` Ken Brown
2014-10-20 12:04 ` martin rudalics
2014-10-20 13:05 ` Ken Brown
2014-10-20 14:11 ` Markus Hoenicka
2014-10-20 14:37 ` Markus Hoenicka
2014-10-20 15:24 ` Eli Zaretskii
2014-10-20 15:29 ` Markus Hoenicka
2014-10-24 21:27 ` Ken Brown
2014-10-24 21:42 ` Markus Hoenicka
2014-12-03 12:43 ` Markus Hoenicka
2014-12-03 14:12 ` Ken Brown
2014-10-20 15:29 ` Eli Zaretskii [this message]
2014-10-07 16:05 ` Markus Hoenicka
2014-07-28 22:45 ` markus.hoenicka
2014-08-06 22:02 ` markus.hoenicka
2014-10-07 16:47 ` Achim Gratz
2014-10-07 18:43 ` Ken Brown
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=83wq7ubvzu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17753@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
--cc=markus.hoenicka@mhoenicka.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 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).