similar to: Problems with .C - [Ff]ree()?

Hi, I am having trouble with some code that I am dyn.loading. I am writing an interface to ARPACK. I compile my interface (dssimp.cc), and link it against the ARPACK library (libarpack_SUN4.a): g++ -shared -static -fPIC dssimp.cc -o dssimp.so -larpack_SUN4 -lg2c -lm I can dyn.load the code and it appears OK. However, when I call my function, the call to the function in the ARPACK library

hello, I am using the following code >s<-"I am very happy, excited, and optimistic.I am very scared, annoyed, and irritated.Iraq?s political crisis entered its second week one step closer to the potential.dissolution of the government, with a call for elections by a vital coalition partner and a suicide attack that extended the spate of violence. that has followed the withdrawal.of

Trying to update a second CentOS box, I'm getting this error repeatedly: [Errno 4] Socket Error: timed out I'm getting this on every mirror and have gone through the list of mirrors more than a dozen times. Oddly, the RPMs I'm trying to upgrade I upgraded just yesterday without a problem on another machine on the same LAN with no problems whatsoever. I can ping mirrors fine. There

On 2/28/16, Linus Torvalds <torvalds at linux-foundation.org> wrote: > The fact is, undefined compiler behavior is never a good idea. Not for > serious projects. Actually, undefined behavior is essential for serious projects, but not for the reasons mentioned. If the language has no undefined behavior, then from the compiler's view, there is no such thing as a bad program. All

Team: My Debian Sarge "testing" box got upgraded from Samba 2.2.6, I believe, to Samba 3 Beta 2 in the latest dist-upgrade supplied spate of updates (90+, and I missed Sambe being in there . . . ). Not a big deal except that now I have lost access to the logon profiles directories at logon time. It's a basic Samba setup. Uses Unix passwords and Unix accounts, etc. Nothing fancy

TL;DR: It's okay to close a bug, if you can justify it properly. Recently there has been a spate of bug-closing with what I would call inadequate documentation. Comments such as "Obsolete?" or "I assume it's fixed" could be applied to nearly every open bug we have. While this does reduce the open bug count--something I have been watching with morbid fascination

KB -- I made those changes several months ago (Sep/Oct I believe), with discussion in IRC. This was after a spate of people in the main channel having issues with Atomic (there's a name that's going to end up causing problems...) and the continued use of RPMForge/RepoForge, with no indication that they're really really bad. As well as the recognition of the reality that there are a

Hola, Estoy intentando descargar datos de la API de ESIOS, de REE, pero estoy teniendo problemas al introducir el token. Estoy usando httr, rCurl y jsonlite. Alguien ha podido descargar los datos? Cómo lo ha hecho? Gracias, Javier [[alternative HTML version deleted]]

Isn't svn set up to auto-parse and post to the bug so you can just say "fixes bug 44444" and it parses it out? I mean, i added that to gcc like 15 years ago, i'm surprised we don't do this :) Nobody should have to add this info manually unless someone forgot to put it in a commit message. On Tue, Jun 12, 2018 at 1:36 PM, Tom Stellard via llvm-dev < llvm-dev at

Hello, We''ve been migrating our fairly large Rails 1.2 application from MRI 1.8.6 to REE 1.8.7, and in the process we''ve encountered some fairly odd behavior. Namely, instead of the expected reduction in memory usage, we''re seeing an increase in memory usage by around 40% and, along with it, an increase in processor usage. The stock 1.8.7 implementation performs

Hi there, We are a software firm based in India. We are a 100% FOSS firm and RoR is one of the core focus areas. We contribute to RoR (and FSF)in various ways - code as well as cash donations. We also publish some how-tos and tech issues on our blogs. We are running a production server on AWS. Here is the howto for REE + passenger + AWS + EBS You can read the full howto here:

Hi all, Thanks to Prof. Ripley, Prof. Gentleman, and Simon Wood (did I miss anyone?). The problem seemed to have gone away. Everyone suggested using some malloc debugger (such as Electric Fence). All I did was following half of what BDR suggested below, i.e., changing all the S_alloc() calls to Calloc() and Free(). I didn't get to try efence, and the problem seems to have disappeared! As

Hola Javier, Hola usuarios, Muchas gracias por contestar y por el interés. Sí es cierto que re-leyendo el correo la información es escasa? Red Eléctrica, a través de ESIOS https://www.esios.ree.es , publica los datos del mercado eléctrico. Estos datos pueden descargarse a través de la web de la API: https://api.esios.ree.es Si ponemos un ejemplo concreto, para saber los precios del

> From: Hin-Tak Leung > > Izmirlian, Grant (NIH/NCI) wrote: > <snipped> > > The only interesting feature is that the tree structure has been > > implemented in C. Its a neater way to carry stuff around and I am > > guessing would make future implementation easier. > > > > Because of its inherent redundancy from the users standpoint, it > >

https://gcc.gnu.org/viewvc/gcc/hooks/ is how it was done. This used the incoming email handling for bugzilla i set up. These days, you could just use bugzilla's rest API IE a simple variant of https://github.com/mozilla/github-bugzilla-pr-linker/blob/master/app/app.py should work as a commit hook. That thing is written as a service, you just need the find/add parts of the rest api, rip

Trying to copy the (binary) header of a input file directly to an output file, I've had repeatable seg faults. The call: writeChar(hdr, outfh, nchars=6144) when hdr just contains one empty string seems to be the culprit. The stack traces weren't all that illuminating, with sig 11 in memory-related functions following this. But in src/main/connections.c it looks like do_writechar

I would like to retrieve a vector of integers from a call to .C(), but I don't know its length in advance. How do I do this without making an ugly safe guess? My vector is called "sequences". I am passing the argument sequences = integer(0) in the call to .C(), then declaring the corresponding argument as int *sequences in my C code. I tried R_alloc()ing the storage in C and

[sending this to R-devel, since it may be of general interest and could possibly lead to better instructions in the "R-exts" manual] Is this another case where only .Call() or .External() [or a fudge factor] solve my problem? Following situation: I use dyn.loaded C code to compute a recursive tree structure from my data. Beforehand I don't know how big the tree will

Dear R-devel, Last week I got several responses to my question about debugging segfaults in my code (original post below). After I changed the S_alloc() calls to Calloc()/Free(), the symptom was gone, but I was told to keep looking. So I did: o Switched to Calloc/Free. Electric Fence did not find any problem. o Put assert(index < bound); assert(index >=0); everywhere in the C routine

Hello, My name is Ick Hoon Jin and I am Ph. D. student in Texas A & M Univ.. When I run the C embedded in R in the Linux system, I confront the following error after 6,000 iteration. By googling I found this error is from the problem in C. *** caught segfault *** address (nil), cause 'memory not mapped' My C code is following: