Opened 17 years ago
Closed 5 years ago
#1648 closed defect (wontfix)
S-57 Update Crash with ATTF
Reported by: | warmerdam | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | closed_because_of_github_migration |
Component: | OGR_SF | Version: | 1.4.0 |
Severity: | normal | Keywords: | s57 |
Cc: | blackmoreb |
Description
ogrinfo crashes when attempting to open JP352BRG.000/001. Traceback:
(gdb) where 5 #0 0x00002aaaaae2e5c1 in DDFField::GetRepeatCount (this=0x0) at ddffield.cpp:207 #1 0x00002aaaab1caecc in S57Reader::ApplyRecordUpdate (this=0x2aaaaeab5010, poTarget=0x60e770, poUpdate=0x663830) at s57reader.cpp:2484 #2 0x00002aaaab1cb2f2 in S57Reader::ApplyUpdates (this=0x2aaaaeab5010, poUpdateModule=0x7fffffe387d0) at s57reader.cpp:2618 #3 0x00002aaaab1cb612 in S57Reader::FindAndApplyUpdates ( this=0x2aaaaeab5010, pszPath=0x51fb30 "JP352BRG.000") at s57reader.cpp:2718 #4 0x00002aaaab1c5b2a in S57Reader::Ingest (this=0x2aaaaeab5010) at s57reader.cpp:444
It appears the update adds some attributes to ATTF, but the .000 file had no ATTF at all.
Change History (8)
comment:1 by , 17 years ago
Status: | new → assigned |
---|
comment:2 by , 17 years ago
Cc: | added |
---|
comment:3 by , 17 years ago
r11628 patches this in 1.4.x branch so there is no crash, though the update is not properly applied. (an error is issued).
comment:4 by , 17 years ago
Milestone: | 1.4.2 → 1.5.0 |
---|
That's all I'm going to do in 1.4.x, so I'm retargetting this to 1.5
comment:5 by , 16 years ago
Milestone: | 1.5.0 → 1.5.1 |
---|
comment:6 by , 10 years ago
If I knew what is "JP352BRG.000/001" I would probably test what happens with GDAL 1.11.
comment:8 by , 5 years ago
Milestone: | → closed_because_of_github_migration |
---|---|
Resolution: | → wontfix |
Status: | assigned → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.
Analysis confirmed. The crash occurs applying this update record:
To this target feature record which has no ATTF:
The correct fix is to create an ATTF field in this situation. The minimum workaround is to avoid a crash in this situation.