search for: r_allocstringbugger

...actual segfault does not -- > pretty sure that means this is a base R bug? submitted here: > https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully i > am not doing something remarkably stupid. the text file itself is 4GB > so cannot upload it to bugzilla, and from the R_AllocStringBugger error > in the previous message, i think most or all of it needs to be there to > trigger the segfault. thanks! I don't want to download the big file or install the archive package. Could you run the code below on the bad file? If you're right and it's only nulls that matter,...

...la3/show_bug.cgi?id=17311 > <https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311> > hopefully i > am not doing something remarkably stupid. the text file itself > is 4GB > so cannot upload it to bugzilla, and from the > R_AllocStringBugger error > in the previous message, i think most or all of it needs to be > there to > trigger the segfault. thanks! > > > I don't want to download the big file or install the archive > package. Could you run the code below on the bad file? If...

...does not -- >> pretty sure that means this is a base R bug? submitted here: >> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully i >> am not doing something remarkably stupid. the text file itself is 4GB >> so cannot upload it to bugzilla, and from the R_AllocStringBugger error >> in the previous message, i think most or all of it needs to be there to >> trigger the segfault. thanks! >> > > I don't want to download the big file or install the archive package. > Could you run the code below on the bad file? If you're right and it&...

...1 >> <https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311> >> hopefully i >> am not doing something remarkably stupid. the text file itself >> is 4GB >> so cannot upload it to bugzilla, and from the >> R_AllocStringBugger error >> in the previous message, i think most or all of it needs to be >> there to >> trigger the segfault. thanks! >> >> >> I don't want to download the big file or install the archive >> package. Could you run the cod...

...e, but prompting the actual segfault does not -- pretty sure that means this is a base R bug? submitted here: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully i am not doing something remarkably stupid. the text file itself is 4GB so cannot upload it to bugzilla, and from the R_AllocStringBugger error in the previous message, i think most or all of it needs to be there to trigger the segfault. thanks! On Sat, Jul 15, 2017 at 10:32 AM, Anthony Damico <ajdamico at gmail.com> wrote: > hi, thanks Dr. Murdoch > > > i'd appreciate if anyone on r-help could help me narro...

hi, thanks Dr. Murdoch i'd appreciate if anyone on r-help could help me narrow this down? i believe the segfault occurs because there's a single line with 4GB and also embedded nuls, but i am not sure how to artificially construct that? the lodown package can be removed from my example.. it is just for file download cacheing, so `lodown::cachaca` can be replaced with `download.file`

...actual segfault does not -- pretty > sure that means this is a base R bug? submitted here: > https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully i am > not doing something remarkably stupid. the text file itself is 4GB so > cannot upload it to bugzilla, and from the R_AllocStringBugger error in the > previous message, i think most or all of it needs to be there to trigger > the segfault. thanks! > > > On Sat, Jul 15, 2017 at 10:32 AM, Anthony Damico <ajdamico at gmail.com> wrote: > >> hi, thanks Dr. Murdoch >> >> >> i'd appreci...

...gt; sure that means this is a base R bug? submitted here: >>> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully i >>> am >>> not doing something remarkably stupid. the text file itself is 4GB so >>> cannot upload it to bugzilla, and from the R_AllocStringBugger error in >>> the >>> previous message, i think most or all of it needs to be there to trigger >>> the segfault. thanks! >>> >>> >>> On Sat, Jul 15, 2017 at 10:32 AM, Anthony Damico <ajdamico at gmail.com> >>> wrote: >>>...

...does not -- pretty >> sure that means this is a base R bug? submitted here: >> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully i am >> not doing something remarkably stupid. the text file itself is 4GB so >> cannot upload it to bugzilla, and from the R_AllocStringBugger error in the >> previous message, i think most or all of it needs to be there to trigger >> the segfault. thanks! >> >> >> On Sat, Jul 15, 2017 at 10:32 AM, Anthony Damico <ajdamico at gmail.com> >> wrote: >> >>> hi, thanks Dr. Murdoch &...

...is a base R bug? submitted here: >>>> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 >hopefully i >>>> am >>>> not doing something remarkably stupid. the text file itself is 4GB >so >>>> cannot upload it to bugzilla, and from the R_AllocStringBugger >error in >>>> the >>>> previous message, i think most or all of it needs to be there to >trigger >>>> the segfault. thanks! >>>> >>>> >>>> On Sat, Jul 15, 2017 at 10:32 AM, Anthony Damico ><ajdamico at gmail.com&g...

...here: > >>>> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 > >hopefully i > >>>> am > >>>> not doing something remarkably stupid. the text file itself is 4GB > >so > >>>> cannot upload it to bugzilla, and from the R_AllocStringBugger > >error in > >>>> the > >>>> previous message, i think most or all of it needs to be there to > >trigger > >>>> the segfault. thanks! > >>>> > >>>> > >>>> On Sat, Jul 15, 2017 at 10:32 AM, Anthon...

...gt; sure that means this is a base R bug? submitted here: >>> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully i >>> am >>> not doing something remarkably stupid. the text file itself is 4GB so >>> cannot upload it to bugzilla, and from the R_AllocStringBugger error in >>> the >>> previous message, i think most or all of it needs to be there to trigger >>> the segfault. thanks! >>> >>> >>> On Sat, Jul 15, 2017 at 10:32 AM, Anthony Damico <ajdamico at gmail.com> >>> wrote: >>>...

...gt; https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 >> >hopefully i >> >>>> am >> >>>> not doing something remarkably stupid. the text file itself is >4GB >> >so >> >>>> cannot upload it to bugzilla, and from the R_AllocStringBugger >> >error in >> >>>> the >> >>>> previous message, i think most or all of it needs to be there to >> >trigger >> >>>> the segfault. thanks! >> >>>> >> >>>> >> >>>> On Sat,...

...ans this is a base R bug? submitted here: >>>> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311 hopefully >>>> i am >>>> not doing something remarkably stupid. the text file itself is 4GB so >>>> cannot upload it to bugzilla, and from the R_AllocStringBugger error in >>>> the >>>> previous message, i think most or all of it needs to be there to trigger >>>> the segfault. thanks! >>>> >>>> >>>> On Sat, Jul 15, 2017 at 10:32 AM, Anthony Damico <ajdamico at gmail.com> >>&...

.../bugzilla3/show_bug.cgi?id=17311 > >> >hopefully i > >> >>>> am > >> >>>> not doing something remarkably stupid. the text file itself is > >4GB > >> >so > >> >>>> cannot upload it to bugzilla, and from the R_AllocStringBugger > >> >error in > >> >>>> the > >> >>>> previous message, i think most or all of it needs to be there to > >> >trigger > >> >>>> the segfault. thanks! > >> >>>> > >> >>>>...