similar to: Child thread libR.so

Simon, Ah, thank you! quiet right. For anyone searching for this in the future, I changed my init fuction to: ---------- SNIP ---------------- void init_r() { SEXP aperm_function; /* this is our version of Rf_initEmbeddedR where we disable stack checking */ const char *init_argv[] = {"MyFront", "--vanilla", "--slave"}; Rf_initialize_R(sizeof

I did some poking around with GDB and confirmed that the advice of setting R_CStackLimit after init, which is echoed in the "threading issues" section of the R-exts help document, isn't entirely useful because init apparently loads the main package which trips over the broken stack checking. Stack trace: #0 R_SignalCStackOverflow (usage=140732197147604) at errors.c:81 #1

A patch for a few more hiccups and trivialities in kinit.c: * The check_path() calls check for "/root" and "/old_root" - I believe that should be "/root" and "/root/old_root". * chdir("/") is recommended after pivot_root() * init_argv[0] isn't set properly to the basename pointed to by char *s - this fix also eliminates six lines of

Following mail advice from maximilian attems (thanks). The following patch changes 2 parts of kinit's command line parameter handling. 1) Parse command line parameters passed to kinit *before* /proc/cmdline, in order to allow overrides 2) Pass this resultant command line to the init program, rather than forcing the kinit caller to pass all /proc/cmdline parameters to the kinit call.

Building on the work in ff0a614bd724f6c4c6a5014a9955dc1bc028f336, this moves the capability code down into the run-init library, so that run-init can use it as well, via the new "-d" flag. Signed-off-by: Kees Cook <kees at outflux.net> --- usr/kinit/Kbuild | 3 +-- usr/kinit/capabilities.h | 10 ++++++++++ usr/kinit/kinit.c | 6 +++---

initramfs-tools wants to validate the real init program before running it, as there is no way out once it has exec'd run-init. This is complicated by the increasing use of symlinks for /sbin/init and for /sbin itself. We can't simply resolve them with 'readlink -f' because any absolute symlinks will be resolved using the wrong root. Add a dry-run mode (-n option) to run-init

systemd supports switching back to the initramfs during shutdown in order to make it easier to clean up the root file system. This is desirable in order to allow us to remove keys from RAM before rebooting, making it harder to obtain confidential information by rebooting into an environment that scrapes RAM contents. --- debian/changelog | 4 +

Dear r-devel members, I encountered a C stack limit issue, when I tried to embed R 2.5 into my application. In the R-exts document, it says:"Note that R's own front ends use a stack size of 10Mb". I desire to know: is it possible to decrease this stack size by modifying R's source code? If it's possible, which part of the source code is responsible for the issue? Thank

Hi, I have tried to disable stack checking by set R_CStackLimit to -1. However, it always crashes my win32 multiple threads program. I am using R-2.5.0. My code looks like: #include <Rversion.h> #if (R_VERSION >= R_Version(2,3,0)) #define R_INTERFACE_PTRS 1 #define CSTACK_DEFNS 1 #include <Rinterface.h> #endif and then, add below line to my main function: R_CStackLimit =

Greetings R developers, R will run a little faster when executing "pure R" code if the function R_CheckStack() is modified. With the modification, the following code for example runs 15% faster (compared to a virgin R-2.5.1 on my Windows XP machine): N = 1e7 foo <- function(x) { for (i in 1:N) x <- x + 1 x }

Hi, As the subject suggests, I am looking for the most robust way to call an (arbitrary) function from the R API from another but the main POSIX thread in a package's code. I know that, "[c]alling any of the R API from threaded code is ?for experts only? and strongly discouraged. Many functions in the R API modify internal R data structures and might corrupt these data structures if

I sent this Email to Chris Lattner and he suggested that I send it to this group. >>After reading your PLDI paper, I found the LLVM Alias Analysis >>Infrastructure page. >> >>It says that there is an implementation of Steensgaard's algorithm >>and your DSA algorithm in the >>"optional poolalloc module". I have searched all over the LLVM

Apparently the way to deal with this error message is to set R_CStackLimit = (uintptr_t)-1 I tried typing this in the R console, but it says Error: object "R_CStackLimit" not found. So where do I type it? In one of the initialization files that R uses when it starts up? I can't find the answer anywhere. Please note that I don't understand words like "DLL" or

I downloaded a binary build of release candidate 2, and it was simply a bare directory tree with no README files or other directions. Does one simply plop this in /usr/local or is there more to it? (I'm on OS X.) -- Perry E. Metzger perry at piermont.com

Hi everyone! I meet one problem when embedding R in C code, when I run the the R code in one child thread , it always print error info: Error: C stack usage is too close to the limit I also try to set R_CStackLimit = (uintptr_t)-1 to disable the C stack check as the R-exts doc say, but it still does not work, the error info still exist. Besides it is interesting that if i

Hello, I have dovecot installed and it works for about 3 hours then I get this error (in /var/log/maillog): Jan 8 08:42:53 stu dovecot: auth(default): pam(grossmsm,69.131.100.47): pipe() failed: Too many open files I set pam_limits.so to allow the user 'dovecot' to have 8192 open files, and I also changed: login_process_size = 512 However, it still wont work for more than a few

Hi all, I'm developing an application on Mac OS X Darwin which embeds R. However, the application always crashes due to the C stack checking. I know that R_CStackLimit can be set to -1 to disable the stack checking, but I don't know where to put the code "R_CStackLimit=-1". Please give some instructions. Thank you very much! Here is my compiler infomation: $g++ -v Using

Hello I'm trying to do an ldap proxy but it is not working, it just continues to access the user's mailbox. I was able to do a proxy with a user in a "passwd-file", but not ldap directory. Here is part my "args" file on the passdb ldap stanza: base = dc=example,dc=com auth_bind = yes pass_filter =

I'm experimenting with a 2.0 setup, using the sieve plugin for 2.0 from mercurial. Without sieve, everything seems to work fine. Once I put in a .dovecot.sieve file, though, nothing gets delivered, with the only hint of what's going wrong being this mess in syslog: Jul 7 13:18:00 bellman dovecot: lda(perry): Panic: file index-transaction.c: line 70 (index_transaction_init): assertion

Stepan, Andreas gave a lot more thought into what you question in your reply. His question was how you can avoid what you where proposing and have proper threading under safe conditions. Having dealt with this before, I think Andreas' write up is pretty much the most complete analysis I have seen. I'd wait for Luke to chime in as the ultimate authority if he gets to it. The