Silverfrost Forums

Welcome to our forums

SDBG64 cannot find any routines

27 Feb 2017 1:36 #18908

I am running an application under the debugger, and I am only able to find a routine in 1 out of 10 times - if I restart the debugger 10 or so times, then the routine search function works. SOURCEPATH is set correctly. Has anyone got this issue? Had this with 8.05 and also with 8.10

27 Feb 2017 2:49 #18911

Do you mean it will not show the routines in the find window or that when it does list them it will not show the source location?


-- Admin Silverfrost Limited
27 Feb 2017 3:31 #18912

It will not show any routines whatsoever. Thanks

27 Feb 2017 5:20 #18914

Is that debugging an FTN95 executable or a DLL (or both)?

28 Feb 2017 2:25 #18924

It is a Fortran executable calling a Fortran DLL. It appears to happen randomly, although in the last 24 hours I haven't been able to get it work at all (i.e. cannot find any routines, so cannot put any breakpoints). Thanks

6 Mar 2017 6:58 #18987

Hello,

I have never been able to set a breakpoint using Control-F in sdbg64. The following program

      integer*4 a,b, mysum
      a=1
      b=2
      mysum=myadd(a,b)
      write(*,*) mysum,a,b
      end
      
      function myadd(a,b)
      integer*4 myadd
      integer*4 a,b
      integer*4 c

      c=a+b
      myadd=c
      return
      end

has been compiled as a 32 bit and 64 bit version using ftn95 8.10.0. Now starting sdbg64 on the 64 bit binary, entering CNTRL-F (for find routine), specifying myadd within the dialog window popping up and pressing the OK button, the system comes up with a new window displaying the line 'myadd (mysum.for: 14)'. If I enter CR to the latter window, Windows comes up with a window stating that sdbg64 would not work any more.

If I do the same to the 32 bit binary (using sdbg, entering myadd + OK) then I am positioned to line 14 of the file (wich is line 'c=a+b') and everything works as expected.

In both cases SOURCEPATH has not been set (by executing 'set SOURCEPATH=' before).

Regards Dietmar

7 Mar 2017 9:32 #18995

There is a more recent build of sdbg64 here: http://www.ftn95.co.uk/ftn95/ftn95-8.10/sdbg64.exe

sdbg64 shouldn't need the source path setting, it should only really be required if there is a change from when the build is completed. sdbg64 doesn't use the sourcepath environment variable (although we can add it). It can take the /sp argument:

sdbg64 test.exe /sp c:\temp\tmpsrc

7 Mar 2017 3:58 #19001

Thanks, this new version of sdbg64 works better.

Regards, Dietmar

Please login to reply.