1 Topic by davidb (edited by davidb 2013-11-01 19:08:49)

Topic: 2.5 Debugger problem

Unfortunately with the new Version 2.5 whenever I issue a "Step over" instruction (e.g. F8) the program stops and Debugger status shows as stopped (large square at bottom left).

Actually its worse. Anything other than step in causes the debugger to stop.

--
David
  • jeff
  • Administrator
  • Offline

Re: 2.5 Debugger problem

David,

I'm not seeing this behavior.  Is there any other information you could provide?  Do you have a simple code sample that exhibits this behavior?

Jeff Armstrong
Approximatrix, LLC

Re: 2.5 Debugger problem

It turns out this behaviour is due to the return of a previous bug in which the command line wasn't being made known to the debugger.

Try stepping though the following with Launch ... arguments on the Options Menu set to JEFF 


PROGRAM HELLO_NAME
   INTEGER :: N
   CHARACTER(LEN=100) :: NAME
   N=COMMAND_ARGUMENT_COUNT()
   ! Quit silently if there are no command line arguments
   IF (N > 0) THEN
      ! Get first argument, assume its a name
      CALL GET_COMMAND_ARGUMENT(1, NAME)
      PRINT *, "HELLO ", TRIM(NAME)
   END IF
END PROGRAM HELLO_NAME

This worked OK in version 2.4.

--
David
  • jeff
  • Administrator
  • Offline

Re: 2.5 Debugger problem

David,

Sorry, there was an unforeseen side effect of changing a minor debugger call.  I have it patched now, and I can send you a patched interface file if you'd like. Otherwise, I'll get a new build of 2.5 together and post it to the site over the next day or two.

Jeff Armstrong
Approximatrix, LLC

Re: 2.5 Debugger problem

That's OK. I can wait for the Patched version to appear on the site.

--
David
  • jeff
  • Administrator
  • Offline

Re: 2.5 Debugger problem

David,

Build 1440 is now available from the Download page, and it should fix this issue.

Jeff Armstrong
Approximatrix, LLC

Re: 2.5 Debugger problem

Thanks. The new build has fixed the problem.

--
David