Topic: SF Package manager bug - crashes!

Hi Jeff,
I went to use the SFPackage manager and found that it immediately crashed with barely a flicker on the screen. I tried to run spfm from the command line and got a fortran error message as follows;
C:\Program Files (x86)\SF Package Manager>sfpm info
SF Package Manager - Fortran Command Line Client 2.2
Copyright 2021, 2022, 2023 Approximatrix, LLC

At line 223 of file .\config.F90
Fortran runtime error: Substring out of bounds: lower bound (0) of 'str' is less than one
Error termination.
I just changed machines and thought that maybe that had somehow caused the problem so i did an uninstall/reinstall but no change. Any help would be appreciated as I use it fairly extensively.
Regards,
Pete

Re: SF Package manager bug - crashes!

Pete,

Thank you for the report.  It looks like the configuration for the package manager is retrieved from the Windows registry, but some fields are incorrect or incomplete.  I'm not sure how that happens.  It leads to a string length calculation that returns zero. 

I'll try to get a fix out today.

Jeff Armstrong
Approximatrix, LLC

Re: SF Package manager bug - crashes!

Thanks Jeff!
Let me know when you've found the time to fix it.
Regards,
Pete

Re: SF Package manager bug - crashes!

Pete,

I apologize for this long delay.  I have a fix, but there was a Simply Fortran bug causing some issues with the fix itself.  It might be another day or two if I can't get this build running today.

Jeff Armstrong
Approximatrix, LLC

Re: SF Package manager bug - crashes!

Pete,

A new installer is available at:

https://download.simplyfortran.com/SFPa … er-2.3.msi

It should fix the problem.  The issue was that, if any settings were detected, it would assume that all settings for the package manager were valid (like the directory where things are stored).  In your case, the settings were not intact for some reason, but the check for valid settings is now more granular.

Jeff Armstrong
Approximatrix, LLC

Re: SF Package manager bug - crashes!

Hi Jeff,
Sorry for the late reply. The latest release fixed the issue. Thanks!
Pete