-
-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] WinGRASS and OSGeo4W g.proj -w fails when not run from shell only #1955
Comments
winGRASS windows console
=> output ok GUI
=> no output
GUI
winGRASS windows console
|
Do the other print options work with |
no crash here. tested above in the GUI. the mysterious thing is:
|
that's the output in the winGRASS windows console:
|
maybe WKT not handled in the python GUI? |
Attached CSV from ProcessMonitor (which is not obvious for me, I'm afraid I know little of Windows internals https://docs.microsoft.com/en-us/sysinternals/downloads/procmon) on running In another context we've seen sf and rgdal having problems with |
Thanks @rsbivand for the CSV file! I found |
Wrong track, according to valgrind there is no buffer overflow in Inspired by rsbivand/rgrass#33 is it possible that the Python GUI for WinGRASS and OSGeo4W GRASS pulls in a different version of GDAL or PROJ? |
|
|
Maybe related to: #1872 ? |
could be |
With latest GRASS 7.8.6-6 from OSGeo4W the following
However, |
This OSGeo4W output is not fine, and only signals that the use of the fallback |
Debugging output from 7.8.6-6 and rgrass7 with fall-back workaround:
Note:
so the same error status that we started with. You can also get the same outcome if rgdal is not installed. |
OK, so this is what is returned in Python:
I notice some encoding issue, in Also:
contains windows line endings. Not sure if that is as it should be... |
I see:
but
in the GRASS GUI Python console (same OSGeo4W 7.8.6-6). |
Hello, |
yes, the bug still exits.
interesting issue, it works on the winGRASS windows console
though it does not work in the GUI console:
|
some random googling |
It looks like there is no difference between GUI and terminal, the segfault happens always on Windows, it's just not visible, because it happens after the WKT string is printed (GUI doesn't show anything in that case for some reason). That suggests the problem is here: and given what the documentation of I suggest this change:
Somewhat related discussion OSGeo/gdal#51 links heap corruption on Windows with not using CPLFree. But obviously I haven't tested this on Windows. Any opinions? |
WinGRASS and OSGeo4W
g.proj -w
in demolocation succeed in outputting WKT only from the shell command prompt. Neither work in the GUI console or throughrgrass7::getLocationProj()
, which reports 884 as the error code; see also rsbivand/rgrass#33.Freshly installed WinGRASS 7.8.6-1 and GRASS 7.8.6 installed in fresh OSGeo4W; fully updated Windows 10.
The text was updated successfully, but these errors were encountered: