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 messages...
Traceback (most recent call last):
File "<string>", ine 3, in <module>
ModuleNotFoundError: No module named 'libstdcxx'
/etc/gdbinit:5: Error in sourced command file:
Error while executing Python code.
There is also a line...
This GDB was configured as "x86_64_pc-msys".
(Shouldn't that be msys2?)
If I ignore the messages and try to debug a terminal application, there are
messages
stating that multiple threads are started, and the application accepts no
keyboard
input, and ultimately must be terminated by closing the window.
It appears there are other development communities negatively impacted by
the fork to mingw-w64. This did not go smoothly.
Perhaps it would be safer to simply provide a version of Rtools42 that
comes with
gdb and msys2?
Dominick
On Wed, Jan 18, 2023 at 2:40 AM Tomas Kalibera <tomas.kalibera at
gmail.com>
wrote:
>
> 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 because incorrect DLL versions were
> installed,
> > in particular, the missing DLL's are: msys-ffi-8.dll and
> > msys-unistring-5.dll.
>
> Try upgrading Msys2 using
>
> pacman -Syuu
>
> Tomas
>
> > Is there an alternative way to install gdb for use with Rtool42?
> >
> > Thanks,
> > Dominick
> >
> > [[alternative HTML version deleted]]
> >
> > ______________________________________________
> > R-devel at r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-devel
>
[[alternative HTML version deleted]]