Please synchronise SDBG and SDBG64

After a program abort, in SDBG one can double click on a line in the stack trace window and the corresponding Fortran source file will be opened and the line(s) with the CALL will be highlighted. In SDBG64, the source line that is highlighted is the first executable statement **after **the CALL.

The call stack window in SDBG does not show source file names and line numbers, as the stack window in SDBG64 does.

The Variables window in SDBG can be sent to the printer, but the text cannot be saved to a file or selected and copied to the clipboard. In SDBG64, even the 'send to printer' capability is missing.

On the other hand, if the same user program (32 or 64 bit) is run from the command line until an exception occurs, the Exception Report pop-up window allows one to copy the traceback report to a file or the clipboard. The pop-up window does show source file and line number information, unlike in SDBG. The line numbers reported by a 64-bit program are those of the next executable statement following a CALL, whereas with a 32-bit program the line numbers are those of the CALLs themselves.

It would be nice to have facilities to copy/save the same kind of details in all four environments (command line vs debugger, 32 vs 64-bit).

Thanks.

One more suggestion but this time to synchronize SLINK and SLINK64:

SLINK MyProg.obj 

produces MyProg.exe while

SLINK64 MyProg.obj 

gives an error and requires

slink64 MyProg.obj /file:MyProg.exe

Thanks Dan. Your suggestion for SLINK64 has been implemented.

1. Another annoying difference between SDBG and SDBG64 which needs to be addressed in SDBG64. When you call

   SDBG64 Prog.exe

and the Prog.exe is missing (say, due to error it was not created by the compiler) the SDBG64 shows couple windows like that which you can not close and leave SDBG64 pressing ESC which is natural and intuitive and how it works with regular 32bit SDBG.

2. The appearance, icons and the buttons of SDBG64 need to be changed to look differently from SDBG. The design of buttons and the color scheme above are extremely obsolete and depressing like on 16-color CGA monitors circa 1980. Changing that look and feel developers themselves will start like their own debugger very much. So far they implicitly cast the message 'True fortraners do not use debuggers'. The new SDBG64 is still not useable, it can debug only if there is no bugs.

The new SDBG64 is still not useable, it can debug only if there is no bugs.

What do you mean?

That statement was missing a smiling. I always tell this when the sdbg64 finds numerous devios bug in my codes it can not decipher causing access violation.

If it does that -- we would like to see it so we can fix the issues.