Am 25.06.2022 um 14:06 schrieb klaus.hasenbach(a)web.de:
For test purposes I deleted all outfile.xxx as suggested (most of
exept one file are deleted anyway when I exit gretl im MS-Windows).
Either I will get the "common outfile error" aigain
Yes, I'm afraid Jack's assessment isn't entirely correct. The problem is
not that something is wrong when gretl exits, but something doesn't work
as expected during the ongoing gretl session.
ore following new
sprintf: format string is missing
*** error in function sanitize_url, line 1
string dqu = sprintf("\"")
OK, this is completely weird (and not reproducible for me when I try
these lines in isolation). My best bet is that after the other error
gretl is deeply confused until it is restarted. Of course this shouldn't
happen, either, but currently isn't so important, perhaps.
Am 25.06.2022 um 09:40 schrieb Riccardo (Jack) Lucchetti:
> This happens on Linux too. The difference is that those
> files should, in theory, be deleted once you exit gretl. Apparently,
> for some reason this is not happening on windows, so some sort of name
> collision occurs.
See above, IMHO the collision doesn't have to do with what happens when
I did some research on what internal functions are called, and it seems
to go down via gretl's gretl_mktemp (in lib/src/gretl_paths.c) to Glib's
g_mkstemp on Windows, and apparently then to Glib's get_tmp_file.
(For example here:
at line 1462, assuming this is the right branch for the glib 2.72
version for gretl on Windows?)
OK, but what does it all mean? It's hard to believe that a pretty core
glib function is the root of the problem, isn't it?