forums.silverfrost.com

[JohnHorspool]

Hi,

Just migrated to a newer machine (still XP by our IT department), and installed FTN95 version 5.10.0

Now, I can compile and run programs okay, but SDBG does not like this machine. I compile on the command line with ftn95/check/undef/debug and even for a simple "hello world" program SDBG fails with the message "Exception 0xE06D7363" in the Call Stack/Status window and assembly language in the other window (instead of source code).

Any ideas please?

John

[PaulLaidler]

Difficult to say what is happening here but you should ensure that there are no old copies of salflibc.dll lying around. Also the current verion is 5.40 and you could try this version.

[JohnHorspool]

Paul,

I uninstalled version 5.1, made sure no old copies of salflibc.dll were lurking anywhere and installed the latest personal version.

I still get the same exception message in the call stack/status window. The other window showing assembly is titled

[Robert]

What command line are you using to invoke the debugger?

[JohnHorspool]

Robert,

I'm compiling with ftn95/check/undef/debug on the command line and invoking SDBG simply with "SDBG prog.exe" , no different to what I have done for as long as I can remember.

cheers,
Jhn

[Robert]

Have you tried using an explicit path for sdbg and the program you want to debug? There is something weird that can happen sometimes with the way Windows decides to load executables.

Also, can you add the /rdc_debug switch to sdbg and send the output to ftn95@silverfrost.com