Opened 17 years ago

Closed 17 years ago

#1804 closed defect (fixed)

KML: Converting simple feature from KML to KML segfaults in KMLDestroyDataSource

Reported by: crschmidt Owned by: Mateusz Łoskot
Priority: normal Milestone:
Component: OGR_SF Version: unspecified
Severity: normal Keywords:
Cc:

Description

crschmidt@bia:~/gdal/ogr$ ./ogr2ogr -f "KML" foo.kml 562.kml Warning 1: Layer name 'Layer #0' adjusted to 'Layer0' for XML validity. Segmentation fault

(gdb) run -f "KML" foo.kml 562.kml Starting program: /home/crschmidt/gdal/ogr/.libs/lt-ogr2ogr -f "KML" foo.kml 562.kml Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1235663168 (LWP 21214)] warning: Lowest section in /usr/lib/libicudata.so.36 is .hash at 000000b4 Warning 1: Layer name 'Layer #0' adjusted to 'Layer0' for XML validity.

Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1235663168 (LWP 21214)] 0xb7d3070c in OGRKMLDataSource::~OGRKMLDataSource () from /home/crschmidt/gdal/.libs/libgdal.so.1 (gdb) bt #0 0xb7d3070c in OGRKMLDataSource::~OGRKMLDataSource () from /home/crschmidt/gdal/.libs/libgdal.so.1 #1 0x08049da4 in main () (gdb) The program is running. Exit anyway? (y or n) y

File attached.

Attachments (3)

562.atom (712 bytes ) - added by crschmidt 17 years ago.
562.kml (1.1 KB ) - added by crschmidt 17 years ago.
previous file was wrong -- thisi s the file i actually used
1804.diff (416 bytes ) - added by Didge 17 years ago.
Patch for that bug

Download all attachments as: .zip

Change History (7)

by crschmidt, 17 years ago

Attachment: 562.atom added

by crschmidt, 17 years ago

Attachment: 562.kml added

previous file was wrong -- thisi s the file i actually used

comment:1 by Didge, 17 years ago

Owner: changed from warmerdam to Mateusz Łoskot

Fix is attached.

by Didge, 17 years ago

Attachment: 1804.diff added

Patch for that bug

comment:2 by crschmidt, 17 years ago

The attached patch did not resolve the segfault. I am recompiling GDAL in debug mode to debug further.

comment:3 by crschmidt, 17 years ago

A clean rebuild with the attached patch did seem to fix it. So, I guess it was just a problem with not having a complete rebuild. Sorry about that.

comment:4 by Even Rouault, 17 years ago

Resolution: fixed
Status: newclosed

Fix commited in r12102

Note: See TracTickets for help on using tickets.