On Feb 13 10:22, Manuel Wienand wrote:
> Hi Corinna,
>
> thanks for the info about the stack sizes.
>
> > [...]
> > pthread_attr_t attr;
> > pthread_attr_init (&attr);
> > pthread_attr_setstacksize (&attr, 1024 * 1024);
> >
> > ret = pthread_create(&threadId, &attr, callGlob,
Hi Corinna,
thanks for the info about the stack sizes.
> [...]
> pthread_attr_t attr;
> pthread_attr_init (&attr);
> pthread_attr_setstacksize (&attr, 1024 * 1024);
>
> ret = pthread_create(&threadId, &attr, callGlob, NULL);
> [...]
Jep, that works for me.
Manuel
On Feb 10 17:24, Corinna Vinschen wrote:
> Other than that, you can change the pthread stacksize since 1.7.10. Try
> this:
>
> > int main(void)
> > {
> > int ret;
> > puts("Starting test");
> >
> > #if 0
> > // Working fine if called in the main thread.
> > callGlob(NULL);
> > #else
> >
Hi Manuel,
please, don't http://cygwin.com/acronyms/#TOFU Thanks.
On Feb 10 13:40, Manuel Wienand wrote:
> Hi Corinna,
>
> ok, the STATUS_STACK_OVERFLOW problem is solved. Seems like a local variable
> with about 540 KiB caused the overflow. The Cygwin Shell gives me 2034 for
> "limit -s" I
NOSORT, NULL, &info );
printf("Found %d files.\n", info.gl_matchc);
for (i=0; i -Original Message-
> From: Corinna Vinschen
> Sent: Tuesday, February 07, 2012 5:46 PM
> Subject: Re: cygwin > 1.7.9: Segmentation faults / STATUS_STACK_OVERFLOW
>
> On F
On Feb 7 17:31, Manuel Wienand wrote:
> Hi,
>
> I have the problem that I get a segmentation fault on the newer versions of
> the cygwin1.dll when debugging and a STATUS_STACK_OVERFLOW exception when
> running without debugger.
> I did an update of my cygwin stuff on Monday, and I'm using the l
6 matches
Mail list logo
