Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
L
libzmq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
libzmq
Commits
17df28d2
Commit
17df28d2
authored
Jun 01, 2018
by
Simon Giesecke
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Problem: outdated information in INSTALL regarding stack size
Solution: removed obsolete information
parent
5ac900a9
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
8 deletions
+1
-8
INSTALL
INSTALL
+1
-8
No files found.
INSTALL
View file @
17df28d2
...
...
@@ -48,14 +48,7 @@ cmake -H. -B<build dir> -G"Visual Studio 14 2015 Win64" \
In
VS
2012
it
is
mandatory
to
increase
the
default
stack
size
of
1
MB
to
at
least
2
MB
due
to
implementation
of
std
::
map
intermittently
requiring
substantial
amount
of
stack
and
causing
stack
overflow
.
ZeroMQ
generally
needs
more
stack
when
FD_SETSIZE
is
higher
.
In
all
Windows
builds
it
is
recommended
to
start
with
at
least
2
MB
stack
size
unless
application
using
ZeroMQ
is
using
large
number
of
threads
which
can
cause
substantial
consumption
of
virtual
address
space
,
especially
if
32
bit
build
is
used
.
Generally
,
programmer
needs
to
tune
the
stack
to
balance
memory
consumption
but
never
get
into
situation
that
stack
is
overflown
.
substantial
amount
of
stack
and
causing
stack
overflow
.
Windows
Builds
-
Static
=======================
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment