forums.silverfrost.com Forum Index forums.silverfrost.com
Welcome to the Silverfrost forums
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Please synchronise SDBG and SDBG64

 
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Suggestions
View previous topic :: View next topic  
Author Message
mecej4



Joined: 31 Oct 2006
Posts: 734

PostPosted: Fri May 05, 2017 1:50 pm    Post subject: Please synchronise SDBG and SDBG64 Reply with quote

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
View user's profile Send private message
DanRRight



Joined: 10 Mar 2008
Posts: 1623
Location: South Pole, Antarctica

PostPosted: Sat Oct 07, 2017 4:16 pm    Post subject: Reply with quote

One more suggestion but this time to synchronize SLINK and SLINK64:
Code:
SLINK MyProg.obj

produces MyProg.exe while
Code:
SLINK64 MyProg.obj

gives an error and requires
Code:
slink64 MyProg.obj /file:MyProg.exe
Back to top
View user's profile Send private message
PaulLaidler
Site Admin


Joined: 21 Feb 2005
Posts: 5007
Location: Salford, UK

PostPosted: Thu Oct 12, 2017 2:05 pm    Post subject: Reply with quote

Thanks Dan. Your suggestion for SLINK64 has been implemented.
Back to top
View user's profile Send private message
DanRRight



Joined: 10 Mar 2008
Posts: 1623
Location: South Pole, Antarctica

PostPosted: Fri Nov 10, 2017 8:54 pm    Post subject: Reply with quote

1) Another annoying difference between SDBG and SDBG64 which needs to be addressed in SDBG64. When you call
Code:
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.
Back to top
View user's profile Send private message
silverfrost
Site Admin


Joined: 29 Nov 2006
Posts: 145
Location: Manchester

PostPosted: Mon Nov 13, 2017 12:05 pm    Post subject: Reply with quote

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

What do you mean?
Back to top
View user's profile Send private message Visit poster's website
DanRRight



Joined: 10 Mar 2008
Posts: 1623
Location: South Pole, Antarctica

PostPosted: Mon Nov 13, 2017 6:31 pm    Post subject: Reply with quote

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
View user's profile Send private message
silverfrost
Site Admin


Joined: 29 Nov 2006
Posts: 145
Location: Manchester

PostPosted: Mon Nov 13, 2017 8:04 pm    Post subject: Reply with quote

If it does that -- we would like to see it so we can fix the issues.
Back to top
View user's profile Send private message Visit poster's website
John-Silver



Joined: 30 Jul 2013
Posts: 603

PostPosted: Thu Nov 16, 2017 9:09 am    Post subject: Reply with quote

SDBG could also be renamed to simply .... DDD ...... for 'Dan's Devilry Detector' Wink lol
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Suggestions All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group