User forums > Help

debugging an R language dll

<< < (2/2)

Andre_Mikulec:
Thanks,

In code::bocks, I ended up doing:

Settings->Debugger-> Common-> [ ] Auto-build project if it is not up-to-date
Settings->Debugger->GDB/CDB debugger->Default-> [ ] Do *not* run the debugger
Projects->MyProject->Build targets->Output filename: W:\R-3.5._\App\R-Portable\bin\i386\Rgui.exe

Debug->Start/Continue
run

Following the R part:
8.4 How do I debug code that I have compiled and dyn.load-ed?
https://cran.r-project.org/bin/windows/base/rw-FAQ.html

the rest happened as I described earlier, except,
I ended up *not having to use* debugbreak.exe.
"RGui->Misc-> Break to Debugger" worked just like it should.

Also, (the GOAL), the usage of code::block's Debugger GUI worked out exactly like it should.

Andre_Mikulec:
Note:
I am working on windows. When I tried Rterm.exe in place of Rgui.exe,  at the Rterm.exe command prompt, I pressed CTRL+C, and control returned to gdb (in code::blocks).  So the control-switching works just like it works for Linux/UNIX people working with gdb (and not windows people where this control switching is expected to 'not work').  I also tried (the goal), breakpoints, and debugging, and that works.

I am not sure who gets the credit for this.
Thanks, R language programmers.   
Thanks "python enabled gdb 8.2" programmers.

I am using R 3.5.2 on Windows 10 Professional on Dell Intel hardware purchased in late 2016.

ollydbg:
Nice to here you solved the problem!

BTW: if you use the GDB from this link: [OT] unofficial MinGW GDB gdb with python released(2018-07-25), then it's me(I build this package).  ;)

Andre_Mikulec:
ollydbg,

Yes, I do use.
[OT] unofficial MinGW GDB gdb with python released(2018-07-25)

It is awesome.

Thanks.

Navigation

[0] Message Index

[*] Previous page