Approximatrix Forums — 2.5 Debugger problem

Re: 2.5 Debugger problem

null@example.com (davidb) — Tue, 05 Nov 2013 19:25:33 +0000

Thanks. The new build has fixed the problem.

Re: 2.5 Debugger problem

null@example.com (jeff) — Tue, 05 Nov 2013 12:50:55 +0000

David,

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

Re: 2.5 Debugger problem

null@example.com (davidb) — Mon, 04 Nov 2013 18:12:20 +0000

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

Re: 2.5 Debugger problem

null@example.com (jeff) — Mon, 04 Nov 2013 14:46:13 +0000

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.

Re: 2.5 Debugger problem

null@example.com (davidb) — Sat, 02 Nov 2013 06:42:14 +0000

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.

Re: 2.5 Debugger problem

null@example.com (jeff) — Sat, 02 Nov 2013 03:27:37 +0000

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?

2.5 Debugger problem

null@example.com (davidb) — Fri, 01 Nov 2013 18:55:27 +0000

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.