Ticket #876 (assigned defect)

Opened 9 years ago

Last modified 9 years ago

s57 applying update with a new ATTF field

Reported by: vaernes@… Owned by: warmerdam
Priority: high Milestone:
Component: OGR_SF Version: unspecified
Severity: major Keywords:
Cc:

Description

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

Changed 9 years ago by warmerdam

Rune,

Could you provide he dataset in question so I could test it?  You can email me
directly with where to find it if the dataset is non-public (warmerdam@pobox.com)

If you have a complete and correct base set and updates, I don't believe an update
should appear for a field that does not already exist.  However, even if the 
source data is in error, I would like to fix GDAL so that it does't bomb out.

Changed 9 years ago by vaernes@…

Frank,

I have sendt you an email with the dataset.
Hope you got it.

Rune

Changed 9 years ago by warmerdam

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?

Changed 9 years ago by vaernes@…

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



Note: See TracTickets for help on using tickets.