I'm moving this sub-thread to the devel list because it's maybe overly
technical/historical for the users list.
On Fri, Jun 24, 2022 at 10:18 AM Riccardo (Jack) Lucchetti
OK, here's a wild guess.
Apparently, there seems to be a problem with the "outfile" command.
Could you please check if there's a file named
"outfile.XXXXXX" in your temporary gretl dir?
That is very unlikely, unless there's a huge bug in GLib. But there
could be files with names on the pattern "outfile.XXXXXX" with the
"XXXXXX" replaced by random characters.
There's some equivocation within libgretl on how exactly to handle
termination of "outfile" , stemming from an attempt to support legacy
"outfile" syntax. It seems to me this can be done cleanly if we give
up that attempt, and work on the assumption that outfile usage is
"current" -- that is, dating from gretl 2018c (September, 2018).
I'll try revising the code in that way and running on Windows 10,
either tomorrow or on Monday.