-
Notifications
You must be signed in to change notification settings - Fork 216
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
seg fault on CRS.to_authority for certain IAU projection codes #1319
Comments
To add internal PROJ debugging: https://pyproj4.github.io/pyproj/stable/advanced_examples.html#debugging-internal-proj |
@snowman2 didn't seem to help, I see a debug call to fopen for proj.ini which succeeds before the segfault |
|
|
Forwarded: OSGeo/PROJ#3828 |
Nice that you found more, I thought I was following the instructions well enough but didn’t know gdb would just work.- Dr. Andrew AnnexOn Jul 17, 2023, at 2:31 PM, Alan D. Snow ***@***.***> wrote:
Forwarded: OSGeo/PROJ#3828
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code Sample, a copy-pastable example if possible
note it's easier to copy/paste the following into ipython
Problem description
Pyproj (or more realistically proj underneath) seg faults when
to_authority
is called for some, but not all, IAU CRSs.In the above code, the crs object is created but calling to_authority (or seemingly repr) causes a segmentation fault and termination of the python process.
Although the information I pasted below was for my m1 mac where I am developing, this issue is also happening in CI builds in ubuntu-latest: https://github.com/AndrewAnnex/planetcantile/actions/runs/5576629154/jobs/10188207849
So it looks like this is probably a relatively recently introduced issue as builds 2-3 months ago were working prior to the recent releases of PyProj/Proj.
Hopefully the call to to_authority is granular enough, due to the segfault it gets annoying to try to see if there is a more diagnostic function that could be used to debug proj from python-land so I haven't dug as deeply as may be possible.
Expected Output
not a seg fault
Environment Information
pyproj info:
pyproj: 3.6.0
PROJ: 9.2.1
data dir: /Users/andrew/mambaforge/envs/morecantile/share/proj
user_data_dir: /Users/andrew/Library/Application Support/proj
PROJ DATA (recommended version): 1.14
PROJ Database: 1.2
EPSG Database: v10.088 [2023-05-13]
ESRI Database: ArcGIS Pro 3.1 [2023-19-01]
IGNF Database: 3.1.0 [2019-05-24]
System:
python: 3.11.4 | packaged by conda-forge | (main, Jun 10 2023, 18:08:41) [Clang 15.0.7 ]
executable: /Users/andrew/mambaforge/envs/morecantile/bin/python
machine: macOS-13.4.1-arm64-arm-64bit
Python deps:
certifi: 2023.5.7
Cython: None
setuptools: 68.0.0
pip: 23.2
Installation method
conda (via mamba)
Conda environment information (if you installed with conda):
Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: