Re: pscoast: GMT_non_zero_winding given non-closed polygon

Hamish <[email protected]> Wed, 20 Aug 2014 21:06:42 +1200
Newsgroups gmane.comp.gis.gmt.user
Message-ID <[email protected]>
Hi,

with regard to these earlier threads about problems with pscoast on
newer versions of Ubuntu and Debian,

  http://gmt.soest.hawaii.edu/boards/1/topics/730
  http://thread.gmane.org/gmane.comp.gis.gmt.user/21512

"""
*** Error in `pscoast': double free or corruption (!prev):
0x00000000025099f0 *** Aborted
"""

I'd like to point to these bug reports:

  https://bugs.debian.org/758685
  https://bugs.launchpad.net/ubuntu/+source/gmt/+bug/1349718

which include a full backtrace I did just now.

note current version of the GSHHS packages there are 2.2.0, and *.cdf
versions are shipped as part of the gmt-gshhs-{low|high|full} packages.

  https://packages.debian.org/sid/all/gmt-gshhs-low/filelist

our compile flags and patches are stored here:
  http://anonscm.debian.org/cgit/pkg-grass/gmt.git/tree/debian?id=debian/4.5.12-1

The patches are not that interesting, just replacing C++ style comments
with /* C */ versions. The compile flag setup can be found in the
debian/rules file at the above git tree browser, and the
proof-in-the-pudding of what compiler flags were used can be found in
the actual build log:

  https://buildd.debian.org/status/fetch.php?pkg=gmt&arch=amd64&ver=4.5.12-1&stamp=1395314222

basically it boils down to:

gcc -fPIC -ansi -pedantic -O2 -I/usr/include \
  -DGMT_SHARE_PATH=\"/usr/lib/gmt/share\" -DGMT_GSHHG_PATH=\"no\" [...]


I tried various things like replacing the coastline files with the
latest GSHHG 2.3.2, and downgrading the default version in configure.ac
(as far as I can see that is just for a string in a warning message),
but no luck, get the same thing. Identical gshhs 2.2.0 cdf files work
fine with GMT 4.5.7 from Debian/stable (wheezy). The trouble started
somewhere between there and Ubuntu 14.04 (GMT 4.5.11).


One wild theory that occurs to me is that instead of the gshhs version
mismatch I was assuming, it is instead the new hardening flags forcing
the program to bail instead of continuing on in an insecure state? So
the double-free() might be real?  (??)



thanks,
Hamish
(DebianGIS team)

ps- I notice in 4.5.11 (ubuntu 14.04) when running a filled contour as
part of the MB-System example scripts the GMT map output is creating
vertical streaks from the patches (in matlab plotting sense) down to
the lower x-axis of the plot window. Is that a known bug? I can provide
more details if needed.

Mailing list for GMT discussions of all kinds.  If you are not sure you have found a bug, discuss it here first.
To formally report bugs or request features, please register and add New Issue on gmt.soest.hawaii.edu
To unsubscribe, send the message "signoff gmt-help" to [email protected]
Note: gmt-help will become obsolete on Sept 1, 2014 - please use forum on gmt.soest.hawaii.edu instead.