#3829 closed defect (fixed)
Segfault in LWGEOM2GEOS
| Reported by: | dbaston | Owned by: | dbaston |
|---|---|---|---|
| Priority: | high | Milestone: | PostGIS 2.0.8 |
| Component: | postgis | Version: | 2.0.x |
| Keywords: | Cc: |
Description
If a GeometryCollection contains an empty geometry followed by a type that can not be read into GEOS, the LWGEOM2GEOS function will call GEOSGeom_destroy on an uninitialized value.
Introduced by fix to #3579.
Change History (5)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
| Owner: | changed from to |
|---|
Good question. If it's not too much of a hassle, I would say apply thru 2.2.
2.1 if you have time. 2.0 I wouldn't bother since I doubt anyone is using that and if they are they should really upgrade anyway as I'm pretty sure there are a lot of fixes we didn't back port because the code is too different.
comment:3 by , 7 years ago
I'd say back to 2.0 branch, if affected. There's a fair amount of bug fixes which already entered 2.0, btw, wouldn't be bad to close 2.0.8 and 2.1.9 …
comment:4 by , 7 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:5 by , 7 years ago
Could you please also add an entry to the NEWS file of each non-trunk branch ?
Fixed in trunk at r15621. How far back should the fix be applied?