Debugging R/Fortran in Windows

[Moved from R-help]
Hi,

I'm trying to debug an R interface to a Fortran subroutine from Windows. 
(Yes, I know I should try Unix/Linux as well, but a quick attempt
suggested that the (MinGW g77) Fortran compiler I have installed on my
Windows laptop works better on this Fortran code.)

I'm trying to follow the instructions in the "Writing R Extensions" Manual:

Start R under the debugger after setting a breakpoint for WinMain.
          gdb .../bin/Rgui.exe
          (gdb) break WinMain
          (gdb) run

But when I run gdb on Rgui.exe, I get the message:
"no debugging symbols found"
and then when I try "break WinMain", I get:
"No symbol table is loaded.  use the 'file' command."
You can also start R normally, load your dll by attaching the package, 
then click on Misc | Break to debugger.

This assumes you have debugging symbols in your DLL, and have gdb set up 
properly; see

http://www.stats.uwo.ca/faculty/murdoch/software/debuggingR

for more details.

Duncan Murdoch
I'm using R 2.1.1 on Windows 2000 and gdb 5.2.1 from MSys's MinGW.

I'm calling a Fortran function (several times) from R.  And I seem to have
the basic two-way data communication working - I appear to have
succesfully passed all required data types (integer, real, double
precision) to and from Fortran with sensible results both from within R
and from using WRITE(FILENUM,*) from within Fortran.  But unfortunately
there is still evidence of memory leakage.

Any suggestions would be greatly appreciated.

Regards,
James

______________________________________________
R-help at stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide! http://www.R-project.org/posting-guide.html
Thanks very much to Uwe, Duncan and Seth (who replied off the list).

Uwe - That section of the R for Windows FAQ was very useful - thanks! 
Sorry I posted a question involving C/Fortran to R-Help.

Duncan - Thanks for all the useful info.  I've bookmarked the pages you
sent me.

Seth - Thanks for suggesting valgrind.  I tried it out, and it correctly
told me that memory leakage was not the problem (although I didn't believe
it at first).

It turned out that the reason my variables were being overwritten was not
because of memory leakage, but because of my own stupidity - using the
same variable name for a function I was estimating and for my current
estimate of that function.  Sorry I didn't spend more time checking this
myself!

Thanks again for your help,
James
Thanks very much to Uwe, Duncan and Seth (who replied off the list).

Uwe - That section of the R for Windows FAQ was very useful - thanks! 
Sorry I posted a question involving C/Fortran to R-Help.

Duncan - Thanks for all the useful info.  I've bookmarked the pages you
sent me.

Seth - Thanks for suggesting valgrind.  I tried it out, and it correctly
told me that memory leakage was not the problem (although I didn't believe
it at first).
Is there a version of valgrind that works in Windows now, or did you do 
this test somewhere else?

Duncan Murdoch
It turned out that the reason my variables were being overwritten was not
because of memory leakage, but because of my own stupidity - using the
same variable name for a function I was estimating and for my current
estimate of that function.  Sorry I didn't spend more time checking this
myself!

Thanks again for your help,
James

______________________________________________
R-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Duncan,
Seth - Thanks for suggesting valgrind.  I tried it out, and it correctly
told me that memory leakage was not the problem (although I didn't
believe it at first).
Is there a version of valgrind that works in Windows now, or did you do
this test somewhere else?

Duncan Murdoch
No, I didn't find a version of valgrind that works on Windows.  I used it
on Linux.

Best wishes,
James