re:locating fault address under debugger

[mcapel]

I have an application that consistently (but rarely) faults at a certain address. How do I associate the fault address provided by the winxp event viewer with a code location in the associated .exe and from there with an actual source line in the associated project?

[Jugoslav_Dujic]

Debug or release configuration?

With Debug (especially if it's an exe file), it's substantially easier -- run the debugger, put a breakpoint anywhere, switch to "Dissassembly view" (make sure you have "ToolsOptionsDebugDisassembly windowSource annotation" and "Symbols" checked). Then, press Ctrl+G (go to) and type the hex address. If your Visual Studio doesn't crash (like mine does), there you are. If it does, repeat the procedure, but don't press Ctrl+G but scroll down manually to the address in question.

If it's release, you can rebuild the application in Release mode with generated debug info (Project/Settings/Fortran/General/Debugging level: Full) and if you're lucky enough to reproduce the crash, just repeat steps as above. If you have JIT enabled in VS, Tools/Options/Debug/Just-in-time debugging, you can even jump to offending line directly after the crash (press Debug or Cancel in the exception message box and Visual Studio will be started immediately).

If all you have is Release .exe without debug info, and it is not reproducible with steps above, then you have a problem -- please repost again if that's the case.

Jugoslav

[mcapel]

I have the debug version of the .exe (i'm the author).

When I hit cntl+G the "go to" dialog comes up and lets me enter a line number...the "go to" dialog wont let me enter an address or an offset. The winxp event viewer provides an address. Do you know what needs to be done to activate the address entry of the "go to" dialog? Thanks for quick response!

[mcapel]

found..the problem (blocked addr entry)...I wasnt in disassembly view.

sorry.