Bug #1162

x2sys seg faults

Added by Mike 5 months ago. Updated 4 months ago.

Status:ClosedStart date:2017-10-19
Priority:NormalDue date:
Assignee:Paul% Done:


Target version:Candidate for next minor release
Affected version:6.x-svn Platform:Mac OS X


x2sys_get -T<Tag> command is crashing like this:

% x2sys_get -TMGD77 | head
ERROR: Caught signal number 11 (Segmentation fault) at
0 libgmt.6.dylib 0x000000010b50af8c gmtlib_write_textrecord + 28
1 ? 0x0000000000000000 0x0 + 0
Stack backtrace:
0 libgmt.6.dylib 0x000000010b4a2ab9 sig_handler + 569
1 libsystem_platform.dylib 0x00007fff65b4bf5a _sigtramp + 26
2 ?
0x00007ffee47680c0 0x0 + 140732731392192
3 libgmt.6.dylib 0x000000010b4d17ec api_put_record_fp + 300
4 supplements.so 0x00000001114634d1 GMT_x2sys_get + 6785
5 libgmt.6.dylib 0x000000010b4bbd87 GMT_Call_Module + 567
6 x2sys_get 0x000000010b49afb9 main + 1017
7 libdyld.dylib 0x00007fff658cb145 start + 1
  1. Search command: x2sys_get -TMGD77
  2. track_ID time drt tz lat lon ptc twt depth bcc btc mtf1 mtf2 mag msens diur msd gobs eot faa nqc

Seems similar to the mgd77list seg fault from a few days ago. If you don't have any x2sys databases on your pc, you could login to lele where they are located in /data/X2SYS.


#1 Updated by Paul 5 months ago

  • Status changed from New to Resolved
  • Assignee set to Paul
  • Target version set to Candidate for next minor release
  • % Done changed from 0 to 100

Fixed several things throughout x2sys in GMT 6 due to the i/o upgrades. Also found that the track/index data in memory was never freed (massive memory leak now plugged). All x2sys tests run again and your x2sys_get command works. r19147.

#2 Updated by Paul 4 months ago

  • Status changed from Resolved to Closed

Closed as fix. Please repost if still problems.

Also available in: Atom PDF