Opened 19 years ago
Closed 9 years ago
#876 closed defect (fixed)
s57 applying update with a new ATTF field — at Version 5
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | OGR_SF | Version: | unspecified |
Severity: | major | Keywords: | |
Cc: |
Description (last modified by )
Hey, I'm sing gdal-1.2.6. When applying a record update with ATTF when the target record does not contain a ATTF field the s57reader segfaults. I'm not sure how to solve this problem, but can I just add the the new field ? Currently I just skip ATTF updates where the target does not contain a ATTF field. Rune.
Change History (5)
comment:2 by , 19 years ago
Frank, I have sendt you an email with the dataset. Hope you got it. Rune
comment:3 by , 19 years ago
Rune, I tried to reproduce this problem (finally!) but things seemed to work OK with GDAL-CVS. I tested it by copying the .000 file, and all the update files (.001 to .006) into the same directory and then ran "ogrinfo" on the base file. For good measure, I did an ogr2ogr copy of all the data and did both operations under "valgrind" to identify any heap corruption issues. All done on Linux. Could you give me any other particulars of your situation?
comment:4 by , 19 years ago
Frank, I'm not sure but maybe my options to the reader plays a part. My settings: LNEM_REFS = OFF RETURN_PRIMITIVES = OFF RETURN_LINKAGES = OFF
comment:5 by , 9 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Frank believed that segfault did not happen any more with GDAL-CVS 9 years ago. No feedback since that, let's believe it is fixed.
Note:
See TracTickets
for help on using tickets.