Re: [Rd] Problem installing gdb into Rtools42

2023-01-19 Thread Tomas Kalibera
On 1/19/23 04:44, Dominick Samperi wrote: > On second thought, there is a lot of metapramming code in Rcpp that > runs before main, so > I was wrong to say nothing can happen before main() is called. > Strategically placed print > statements may be the best strategy. You can insert breakpoints

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Dirk Eddelbuettel
On 18 January 2023 at 22:44, Dominick Samperi wrote: | On second thought, there is a lot of metapramming code in Rcpp that runs | before main, so | I was wrong to say nothing can happen before main() is called. | Strategically placed print | statements may be the best strategy. Yes, and if you

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Dominick Samperi
On second thought, there is a lot of metapramming code in Rcpp that runs before main, so I was wrong to say nothing can happen before main() is called. Strategically placed print statements may be the best strategy. On Wed, Jan 18, 2023 at 8:17 PM Dominick Samperi wrote: > Since these “stray

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Dominick Samperi
There may be a more serious problem with gdb, or perhaps a very subtle problem in the RInside package repl function that only appears under Windows (I reported this in the Rcpp-devel list, where I provided a small example repl.cpp with Makefile for Windows). Gdb is invoked as 'gdb repl.exe', a

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Dominick Samperi
There may be a more serious problem with gdb, or perhaps a very subtle problem in the RInside package repl function that only appears under Windows (I reported this in the Rcpp-devel list, where I provided a small example repl.cpp with Makefile for Windows). Gdb is invoked as 'gdb repl.exe', a

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Tomas Kalibera
On 1/18/23 19:41, Dominick Samperi wrote: > Thanks for the detailed feedback Tomas, > > I ran the command 'pacman -Syuu' again, just to be sure, and this time > it says "there is nothing to do." > > It appears that gdb is working. I was spooked by the diagnostics that > you say is a known (not

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Dominick Samperi
Thanks for the detailed feedback Tomas, I ran the command 'pacman -Syuu' again, just to be sure, and this time it says "there is nothing to do." It appears that gdb is working. I was spooked by the diagnostics that you say is a known (not serious) issue. My mistake was not setting a breakpoint

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Tomas Kalibera
On 1/18/23 17:39, Dominick Samperi wrote: > Thanks, > > But this didn't work. It installs msys2 along with lots of other > stuff, and gdb would not start as before (missing DLL's). > > Then I tried to run the command you suggested again, and there was a > warning from the package manager about a

Re: [Rd] Problem installing gdb into Rtools42

2023-01-18 Thread Dominick Samperi
Thanks, But this didn't work. It installs msys2 along with lots of other stuff, and gdb would not start as before (missing DLL's). Then I tried to run the command you suggested again, and there was a warning from the package manager about a cycle detected, but now gdb starts with the following

Re: [Rd] Problem installing gdb into Rtools42

2023-01-17 Thread Tomas Kalibera
On 1/18/23 04:33, Dominick Samperi wrote: Hello, I tried installing gdb into Rtools42 following the instructions here https://cran.r-project.org/bin/windows/base/howto-R-4.2.html I ran 'pacman -Sy gdb', and the installation seemed to complete without problems. But gdb could not be started

[Rd] Problem installing gdb into Rtools42

2023-01-17 Thread Dominick Samperi
Hello, I tried installing gdb into Rtools42 following the instructions here https://cran.r-project.org/bin/windows/base/howto-R-4.2.html I ran 'pacman -Sy gdb', and the installation seemed to complete without problems. But gdb could not be started because incorrect DLL versions were installed,