[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17753: Cygwin emacs-X11 core dump
From: |
Eli Zaretskii |
Subject: |
bug#17753: Cygwin emacs-X11 core dump |
Date: |
Mon, 20 Oct 2014 18:29:09 +0300 |
> 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.
- bug#17753: Cygwin emacs-X11 core dump, (continued)
- bug#17753: Cygwin emacs-X11 core dump, Markus Hoenicka, 2014/10/20
- bug#17753: Cygwin emacs-X11 core dump, Markus Hoenicka, 2014/10/20
- bug#17753: Cygwin emacs-X11 core dump, Eli Zaretskii, 2014/10/20
- bug#17753: Cygwin emacs-X11 core dump, Markus Hoenicka, 2014/10/20
- bug#17753: Cygwin emacs-X11 core dump, Ken Brown, 2014/10/24
- bug#17753: Cygwin emacs-X11 core dump, Markus Hoenicka, 2014/10/24
- bug#17753: Cygwin emacs-X11 core dump,
Eli Zaretskii <=
bug#17753: Cygwin emacs-X11 core dump, Markus Hoenicka, 2014/10/07
Message not available