Bug #555

grdtrack -E multiple lines crashes

Added by Gwen about 3 years ago. Updated about 3 years ago.

Status:ClosedStart date:2014-05-07
Priority:NormalDue date:
Assignee:Paul% Done:

0%

Category:-
Target version:Candidate for next bugfix release
Affected version:5.1.1 Platform:Mac OS X

Description

Attempting to enter multiple lines to the -E argument of grdtrack results in an error.

This command runs fine:

gmt grdtrack -GESP_032711_1955.lowpass.grd -E184.3181/15.2303+l0.5k+o45+d > track.txt

Both of the following commands crash. Note that the first command is what I want to be able to do; to have the same center point and have radial lines at different angles from that point. I tested the second command also since the documentation seems to possibly indicate all the flags being at the end, although that would not allow me to do the lines I want, since I want different angles from the same point.

gmt grdtrack -GESP_032711_1955.lowpass.grd -E184.3181/15.2303+l0.5k+o45+d,184.3181/15.2303+l0.01k+o90+d > track.txt
gmt grdtrack -GESP_032711_1955.lowpass.grd -E184.3181/15.2303,184.3181/15.231+l0.01k+o90+d > track.txt

Both commands crash with the identical error:

grdtrack: Syntax error -Q: Valid coordinate codes are [lcr][bmt] and z[+-]
ERROR: Caught signal number 11 (Segmentation fault) at
0 libgmt.5.1.1.dylib 0x000000010b6e660e GMT_grdtrack + 2574
1 ??? 0x0000000000000008 0x0 + 8
Stack backtrace:
0 libgmt.5.1.1.dylib 0x000000010b52908b sig_handler + 347
1 libsystem_platform.dylib 0x00007fff884415aa _sigtramp + 26
2 ??? 0x0000000000000000 0x0 + 0
3 libgmt.5.1.1.dylib 0x000000010b53acb3 GMT_Call_Module + 835
4 gmt 0x000000010b51f7ec main + 1228
5 libdyld.dylib 0x00007fff8ccb85fd start + 1

Thanks for your consideration of this error.

Associated revisions

Revision 13119
Added by Paul about 3 years ago

Fix problem in issue #555 where pos2 was not reset for each separate line

History

#1 Updated by Paul about 3 years ago

  • Status changed from New to Resolved
  • Assignee set to Paul
  • Target version set to Candidate for next bugfix release

The problem was that a local variable (pos2) was not reset to 0 before each new line (only the first one), and this lead us astray and into the bad message. Should be fixed in r13119, let me know. Note only one +d is needed as it is a global modifier.

#2 Updated by Paul about 3 years ago

  • Status changed from Resolved to Closed

Closing this on as fixed.

Also available in: Atom PDF