Displaying 3 results from an estimated 3 matches for "r_cstackdir".
2016 Feb 01
1
Wrong config check for __libc_stack_end
...id *);
(void) sysctl(nm, 2, &base, &len, NULL, 0);
R_CStackStart = (uintptr_t) base;
}
#else
if(R_running_as_main_program) {
/* This is not the main program, but unless embedded it is
near the top, 5540 bytes away when checked. */
R_CStackStart = (uintptr_t) &i + (6000 * R_CStackDir);
}
#endif
if(R_CStackStart == -1) R_CStackLimit = -1; /* never set */
/* printf("stack limit %ld, start %lx dir %d \n", R_CStackLimit,
R_CStackStart, R_CStackDir); */
}
#endif
so I'd hope that typically R_CStackStart would be set usefully
also when the __libc_...
2016 Feb 01
3
Wrong config check for __libc_stack_end
>>>>> Alba Pompeo <albapompeo at gmail.com>
>>>>> on Fri, 29 Jan 2016 08:23:26 -0200 writes:
> Here is my log from 'make check' using an Intel i5 64-bit
> processor - http://pastebin.com/raw/N6SYAuFX Here is
> Isaac's log from 'make check' using an Intel Atom 32-bit
> processor -
2006 Apr 11
4
Stack checking, core dumps, and embedding R
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been experiencing some interesting stack warnings recently when
moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0 series. In
particular, I'm getting warnings of "Error: C stack usage is too close
to the limit" before