View previous topic :: View next topic |
Author |
Message |
DanRRight
Joined: 10 Mar 2008 Posts: 2815 Location: South Pole, Antarctica
|
Posted: Thu Oct 10, 2019 8:20 pm Post subject: |
|
|
When the error happens the code launches SDBG64 which stops on offending line shown in violet.
But the color of background of line is extremely badly chosen. You can not see anything there. Good variants are shown at the corner. This definitely has to be changed
/* Sick how damn conservative users of all versions of Fortran are. Almost no one uses excellent tool called debugger. Same for reporting bugs, let alone giving any suggestions for improvement...Is this difficult to type instead of
Code: | C:> SDBG Program.exe |
adding just the key /DEBUG or /FULL_DEBUG when do the compilation to usual /CHECk and possibly /UNDEF ?
Code: | C:> FTN95 Program.f95 /DEBUG /CHECK /UNDEF |
|
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Sat Oct 26, 2019 11:04 am Post subject: |
|
|
I think you mean SDBG rather than SDBG64. The violet is showing you that it is the current execution point and that there is a breakpoint on that line. I admit it doesn't look ideal. SDBG64 doesn't vary the execution point line colour but you can see it is a breakpoint in the left margin. |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Sat Oct 26, 2019 11:37 am Post subject: |
|
|
Dan: have the 'sdbg64 showing the wrong line' issues been fixed now by using the latest FTN95? |
|
Back to top |
|
|
DietmarSiepmann
Joined: 03 Jun 2013 Posts: 279
|
Posted: Mon May 31, 2021 4:28 pm Post subject: |
|
|
I would like to make use of routines
Code: | C_EXTERNAL GetLibraryVersionInfo '_GetLibraryVersionInfo'():INTEGER(7)
C_EXTERNAL GetLibraryDateInfo '_GetLibraryDateInfo'():INTEGER(7)
C_EXTERNAL GetString 'GET_CSTRING@'(REF,VAL,REF)
|
mentioned above by Dan, because these routines could be used to provide for a way to check if the version number of dlls clearwin64.dll and salflibc64.dll loaded by an application is in sync with the version number of the dlls with respect to which the application in question has been built.
I would appreciate very much if they were part of the official release.
Regards,
Dietmar |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
|
Back to top |
|
|
DietmarSiepmann
Joined: 03 Jun 2013 Posts: 279
|
Posted: Tue Jun 01, 2021 9:35 am Post subject: |
|
|
Paul,
thanks for your information. I did know this request but that was not my problem.
In the request you mentioned in your last post there appeared 2 ways of retrieving information about the SALFORD dlls loaded. One by Dan and one by JohnC. And they were different (e.g. with respect to the routine names and data types returned by the functions in question). I did not make it to use the routines mentioned by JohnC when calling from an app built with INTEL 64 bit compiler ifort and hence tried the ones mentioned by Dan which worked.
However, I am not sure if they are part of the official release. E.g. for ftn95 version 8.63 I tried to search for string "GetLibraryVersionInfo" in the online help (called via ftn95 --help) and did not find it.
Hence do I understand you right that GetLibraryVersionInfo, GetLibraryDateInfo and GET_CSTRING@ are contained in the release of ftn95 (8.63 and higher)?
Regards,
Dietmar |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
Posted: Tue Jun 01, 2021 10:15 am Post subject: |
|
|
Dietmar
These routines are permanently in the FTN95 library. They are located in salflibc.dll and clearwin64.dll. |
|
Back to top |
|
|
|