search for: do_readdcf

...7 17:40 NAMESPACE drwxr-sr-x 2 root 33 4096 Dec 17 17:19 R drwxr-sr-x 2 root 33 4096 Dec 17 05:58 libs So, is dcf.c, or main.c the better place to check. dcf.c does not look like "fun" - all those lexical arguments at the start: SEXP attribute_hidden do_readDCF(SEXP call, SEXP op, SEXP args, SEXP env) { .... man many lines .... } else { /* Must be a regular line with no tag ... */ line[20] = '\0';...

...ling the packages doesn't seem to have any effect on this outcome. Here's the first few lines of a gdb backtrace: #0 0xff132df8 in strlen () from /usr/lib/libc.so.1 #1 0xfe612bcc in Rf_mkChar (name=0x12a46d9 <Address 0x12a46d9 out of bounds>) at dstruct.c:102 #2 0xfe5f5f40 in do_readDCF (call=0x0, op=0xffffffff, args=0x950ce0, env=0x954370) at dcf.c:109 #3 0xfe64d010 in do_internal (call=0xfe7694f4, op=0x12b9c4, args=0x950ce0, env=0x9503b8) at names.c:1020 (I can provide the full trace if desired) Has anyone else found problems with embedded R with version 1.5.0? Did...

...p')" will cause a segfault in do_strsplit (character.c:260) because the regmatch structure contains the nonsense values: (gdb) print regmatch[0] $1 = {rm_so = 9257728, rm_eo = 9257729} With R 1.5.0, R fails to complete startup initialization under both rpy and RSPython, segfaulting in do_readDCF (dcf.c:109) with similar nonsense values in the regmatch structure: (gdb) print regmatch $7 = {{rm_so = 9777896, rm_eo = 9777905}} Does anyone have asuggestion on the best way to track down the cause of this problem? I'll be happy to provide tracebacks, core dumps, etc if that would help...

...R > drwxr-sr-x 2 root 33 4096 Dec 17 05:58 libs > > So, is dcf.c, or main.c the better place to check. dcf.c does not look like "fun" - all those lexical arguments at the start: Cue story of looking for keys under lamppost... > > SEXP attribute_hidden do_readDCF(SEXP call, SEXP op, SEXP args, SEXP env) > { > .... man many lines .... > } else { > /* Must be a regular line with no tag ... */ > line[20] = '\0'; >...

...33 4096 Dec 17 05:58 libs >> >> So, is dcf.c, or main.c the better place to check. dcf.c does not look like "fun" - all those lexical arguments at the start: > > Cue story of looking for keys under lamppost... > >> >> SEXP attribute_hidden do_readDCF(SEXP call, SEXP op, SEXP args, SEXP env) >> { >> .... man many lines .... >> } else { >> /* Must be a regular line with no tag ... */ >> line[20] = '\0'; >...

On 17/12/2015 9:06 AM, Michael Felt wrote: > More experimenting with calling commands: > > tools:::foobar() > Error: Line starting 'Package: tools ...' is malformed! > > tools::foobar() > Error: Line starting 'Package: tools ...' is malformed! These both do a loadNamespace("tools"). > > Tools:::foobar() > Error in loadNamespace(name)