This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Or just use ulimit -s to set the default thread stack size smaller, maybe?
The problem wasn't the maximum stack size, but the minimum/initial
size, which was bumped from 16 kB to 2 MB. So even if you are very
careful in your thread handler(s) to not consume too much stack space,
you still eat up at least 2 MB per thread...
With threads, the initial stack size *is* the max size, since each thread's stack address space must be contiguous and is not relocatable.
So I suspect ulimit -s would indeed help. - Dan
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |