<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">
<TITLE>RE: [mpich-discuss] Debugging</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2> Hi,<BR>
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).<BR>
Valgrind should help.<BR>
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 --> *).<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: owner-mpich-discuss@mcs.anl.gov [<A HREF="mailto:owner-mpich-discuss@mcs.anl.gov">mailto:owner-mpich-discuss@mcs.anl.gov</A>] On Behalf Of Gib Bogle<BR>
Sent: Friday, May 02, 2008 12:45 AM<BR>
To: mpich-discuss@mcs.anl.gov<BR>
Subject: [mpich-discuss] Debugging<BR>
<BR>
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.<BR>
Also, should I be able to compile with lower optimization than /O3? This same program (release<BR>
version) runs with /O3 or /O2 but when it is built with /O1 an array subscript goes out of bounds.<BR>
<BR>
Would valgrind be helpful?<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>