If you really have succeeded (and I do not hold you to it), then I'm sure that everyone in your forum will be extremely interested in what exactly this problem has been, how you diagnosed it and how on earth you managed to cure it.
---
John

I think I've got the debugger-only crashing fixed in regards to the file dialog. I'll send you an email sometime today with the new WFDialogs library to try out.

I've sent you an email with a possibly fixed version of the Windows Fortran Dialogs  package that might eliminate the debugger-only crash circumstance.  I'm hopeful it works.

Some searching on the Internet shows that there are quite a few people experience crashes when calling GetOpenFileName or GetSaveFileName (the functions that actually opens a file dialog in Windows) in programs being debugged in the GNU Debugger (Simply Fortran's underlying debugging engine).  I'll see what solutions I can find.

It sounds like the core of the issue is that using standard Windows file dialogs in conjunction with Simply Fortran's debugger causes a crash in the program being debugged.  I was able to replicate the crash on my system originally, so I'll try to investigate more.  I don't have an immediate guess as to what's occurring, though.

      SUBROUTINE GetFileName(ChangePath)
C     ----------------------------------
C     jw / 25-07-12  1st draft started
C     jw / 15-02-14  last rev.

C     On returning from this subroutine:

C The INPUT file pathname should be stored in
C TRIM(F%Path)//TRIM(F%Name)//'.'//TRIM(F%I%Ext).

C     F%I%Exists should indicate whether 
C     the INPUT file already exists.
C     F%I%OPEN should indicate whether 
C     it is already open.

C     F%bakExists should indicate whether
C     a BAK file already exists.
C     (It should not be open).

C     F%O%Exists should indicate whether 
C    the OUTPUT file already exists.
C     F%O%OPEN should indicate whether 
C     it is already open.

      USE Dislin
      USE Files
      USE wfdialogs
      LOGICAL EXISTS, ChangePath

C     IF(F%Named) RETURN

C     Input filename not yet known
      F%Path = ('      ')
      F%Name = (' ')
      F%I%Exists = .FALSE.
      F%I%OPEN = .FALSE.
      F%BAKexists = .FALSE.
      F%BAKdeletable = .FALSE.

      CALL SWGOPT('STANDARD','DIALOG') !Use STANDARD file dialog boxes
C     Prompt user for a data input Path\filename.ext
      F%Path = ' '

10    IF(RequestOpenFile(F%Path,
     +'Default DATA file type','*.ins',
     + 'Enter or select a structure DATA filename')) THEN
          CALL SWGOPT('TOP','DIALOG')!Keep all other dialog boxes on top

          CALL ParsePath(F%PATH,F%Name,F%I%Ext)
          IF(LEN_TRIM(F%I%Ext).EQ.0) F%I%Ext='ins'
          F%O%Ext = 'rtf'
          F%Named = .TRUE.

C         Set the current directory to that of the chosen file
          IF(ChangePath) CALL CHDIR(F%Path,iDone)
          :
          :
          : {more}
          :
          :
          :

The crash happens mid-way through the process of drawing and populating the filename requester dialog box.  At first, it managed only to draw the box outline and insert the title-bar caption, 'Enter or select a structure DATA filename', but the box was empty.  When I commented out the next line, viz,

          CALL SWGOPT('TOP','DIALOG')!Keep all other dialog boxes on top

this enabled the dialog box to start to fill, with about 30% of its normal content being written into it before the crash.

The crash does not happen when running outside the debugger.

If you have time to look into this any further and would like the latest version of my project code, please let me know and I'll send it.
---
John

At what point does the program crash now?  Is it when the file dialog is opened?

I am still getting this SIGSEGV fault on a project whenever I use the debugger, on a program which compiles, links, loads and runs without error when not debugging.  This is after switching away from DISLIN for filename requester dialogs and using Jeff's very neat routines instead.

If anyone else has the same experience, it might be helpful to hear about it.

I see the Package Manager mentions that is 32/64.  I should have noticed that.
This is an extremely helpful development for SF.
I do hope you can continue to add to this library. 
I think you should also mention it in SF "news".
---
J.

I've added the file dialog title argument like you suggested.  Also, it now allows requesting text entry or selection from a list via simple calls.  The latest version is available in the Package Manager.

It already supports 64-bit projects.  Just switch your project to 64-bit and compile.  It should work fine.

I'd appreciate also a 64bit version.

I like the way that, as well as accepting a filename extension filter, the the filename requester dialog also accepts a string for naming or describing the default file type.

Small suggestion:
The filename requester dialog box could benefit from a text string parameter that can be passed to it, to display in the top bar.  I was using this in the DISLIN version to display a prompt.
---
John

If you're interested in trying, I've built a small library that provides a file open and save dialog from Fortran that doesn't seem to crash.  It is not an exact replica of DISLIN's functions, but it is similar enough:

http://packages.simplyfortran.com/package/72.html

There is no example project included, but the documentation can be viewed at:

https://bitbucket.org/ArmstrongJ/wfdialogs/overview

and an example program can be seen at:

https://bitbucket.org/ArmstrongJ/wfdial … ?at=master

When linking, you'll need to remember to add the flags:

-lwfdialogs -lcomdlg32

Hopefully you can just use these calls rather than the problematic DISLIN call.