| View previous topic :: View next topic |
| Author |
Message |
mecej4
Joined: 31 Oct 2006
Posts: 1896
|
 Posted: Fri May 05, 2017 1:50 pm Post subject: 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. |
|
| Back to top |
|
 |
DanRRight
Joined: 10 Mar 2008
Posts: 2866
Location: South Pole, Antarctica
|
| Posted: Sat Oct 07, 2017 4:16 pm Post subject: |
|
|
One more suggestion but this time to synchronize SLINK and SLINK64:
produces MyProg.exe while
gives an error and requires
| Code: | | slink64 MyProg.obj /file:MyProg.exe |
|
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 8018
Location: Salford, UK
|
| Posted: Thu Oct 12, 2017 2:05 pm Post subject: |
|
|
| Thanks Dan. Your suggestion for SLINK64 has been implemented. |
|
| Back to top |
|
|
DanRRight
Joined: 10 Mar 2008
Posts: 2866
Location: South Pole, Antarctica
|
| Posted: Fri Nov 10, 2017 8:54 pm Post subject: |
|
|
1) Another annoying difference between SDBG and SDBG64 which needs to be addressed in SDBG64. When you call
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. |
|
| Back to top |
|
|
silverfrost
Site Admin
Joined: 29 Nov 2006
Posts: 191
Location: Manchester
|
| Posted: Mon Nov 13, 2017 12:05 pm Post subject: |
|
|
> The new SDBG64 is still not useable, it can debug only if there is no bugs.
What do you mean? |
|
| Back to top |
|
|
DanRRight
Joined: 10 Mar 2008
Posts: 2866
Location: South Pole, Antarctica
|
| Posted: Mon Nov 13, 2017 6:31 pm Post subject: |
|
|
| 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. |
|
| Back to top |
|
|
silverfrost
Site Admin
Joined: 29 Nov 2006
Posts: 191
Location: Manchester
|
| Posted: Mon Nov 13, 2017 8:04 pm Post subject: |
|
|
| If it does that -- we would like to see it so we can fix the issues. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
