Re: [Rd] segfault after .C call.

2011-10-07 Thread alex
Have you ever tried to use .Call instead of .C? my segfault-problem was solved by using .Call but I am just a beginner and can not explain why this is Alex -- View this message in context: http://r.789695.n4.nabble.com/segfault-after-C-call-tp3872557p3881461.html Sent from the R devel mailing li

Re: [Rd] segfault after .C call.

2011-10-04 Thread Simon Urbanek
The bug is in your code! (I see at least one - many buffer overflows in all char** output arguments). Please don't abuse the bug tracking system for usage questions. You may want to consider using either .Call (if you are familiar with R) or Rcpp (if you are more familiar with C++), .C is not th

[Rd] segfault after .C call.

2011-10-04 Thread Adrin
Hi there, I think I'm encountering a bug, and I already reported it here: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14695 But meanwhile, could you help me by any suggestions about the problem? I'll place the content of the reported bug here. You can find attachments on bugzilla if you