search for: 1dq20lw4vyh1s

...../library/tools/R/tools.rdb] Error 139 make[1]: *** [Makefile.win:33: R] Error 1 make: *** [Makefile:18: all] Error 2 It looks to have compiled its own Rterm.exe, and segfaults when running it? On 2020-08-21 18:48:42 murdoch.duncan at gmail.com wrote: > > On 21/08/2020 12:53 p.m., m15g9g+1dq20lw4vyh1s--- via R-devel wrote: > > Thanks for the response. Having spent a lot of the day trying to solve > this, as R is essential for my workflow, I've tried to debug via the binary > only as I haven't yet got the toolchain working - I'm quite inexperienced > at this. > >...

...sion? The bug > report mentions Registry key > > HKCU\Software\Microsoft\InteliPoint\AppSpecific\Rgui.exe > > which I believe is installed by the Microsoft R Client rather than the > CRAN distribution of R. > > Duncan Murdoch > > On 21/08/2020 12:53 p.m., m15g9g+1dq20lw4vyh1s--- via R-devel wrote: > > Thanks for the response. Having spent a lot of the day trying to solve > this, as R is essential for my workflow, I've tried to debug via the binary > only as I haven't yet got the toolchain working - I'm quite inexperienced > at this. > >...

Thanks for the response. Having spent a lot of the day trying to solve this, as R is essential for my workflow, I've tried to debug via the binary only as I haven't yet got the toolchain working - I'm quite inexperienced at this. I've confirmed the problem is exactly as described in the initial (albeit old) bug report. The exception that's thrown within Visual Studio is: