Opened 17 years ago
Last modified 17 years ago
#15 closed defect (fixed)
Double free causes segfault
Reported by: | pramsey | Owned by: | pramsey |
---|---|---|---|
Priority: | high | Milestone: | PostGIS 1.3.6 |
Component: | postgis | Version: | 1.3.X |
Keywords: | Cc: |
Description
Cliff Wright writes:
I did not isolate the exact comparison, however the core dump did indicate which line and file caused the problem. looking at the code I see a memory free was called apparently pointing at the wrong object. The same free is used a couple of lines later pointing at the correct object. The patch attached shows the fix I used. I was using version 1.3.1, however see the same bug in subversion.
Attachments (1)
Change History (2)
by , 17 years ago
Attachment: | patcha.txt added |
---|
comment:1 by , 17 years ago
Yup, that looks entirely straightforward and sensible. I'm guessing that this is within the function LWGEOM_same (it's a little bit tricky to tell without your test query ;). Applied to SVN.
ATB,
Mark.
http://postgis.googlecode.com/issues/attachment?aid=-296287623309024258&name=patcha.txt