[mpich-discuss] Debugging

[Jayesh Krishna]

 Hi,
  The problem that you see might not be related to building debug version
of your code (It could some race condition bug which manifests in debug
version - due to the compiler-added code).
  Valgrind should help.
  I would also recommend that you turn on the "run time error checking"
(esp "Check Array and String bounds") when compiling your program
("Configuration properties" --> Fortran --> Run-time --> *).

Regards,
Jayesh

-----Original Message-----
From: owner-mpich-discuss at mcs.anl.gov
[mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of Gib Bogle
Sent: Friday, May 02, 2008 12:45 AM
To: mpich-discuss at mcs.anl.gov
Subject: [mpich-discuss] Debugging

Should I expect to be able to build an Intel Fortran debug executable on
Windows?  When I do this with a program that runs in the release version,
the debug version fails with an access violation. 
Also, should I be able to compile with lower optimization than /O3?  This
same program (release
version) runs with /O3 or /O2 but when it is built with /O1 an array
subscript goes out of bounds.

Would valgrind be helpful?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20080502/1be78864/attachment.htm>