Bug #1033

Segmentation fault

Added by Marcelo 3 months ago. Updated 3 months ago.

Status:ClosedStart date:2017-01-20
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:-
Target version:Candidate for next bugfix release
Affected version:5.x-svn Platform:

Description

Last gmt5 that I successfully compile from svn was r17362.

After that, when I run any simple command it results in a segmentation fault.

Comparing my cmake log from r17362 and r17457:

$ diff cmake17362.log cmake17457.log
321c321
< -- Performing Test HAVE_BUGGY_SINCOS - Failed
---
> -- Performing Test HAVE_BUGGY_SINCOS - Success

from gdb:

$ gdb gmt
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying" 
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gmt...(no debugging symbols found)...done.
(gdb) run psbasemap -R0/20/0/10 -Jx1c -Ba5f1
Starting program: /opt/gmt/5.4.0/bin/gmt psbasemap -R0/20/0/10 -Jx1c -Ba5f1
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff788d6c4 in sincos () from /opt/gmt/5.4.0/lib/libgmt.so.5
(gdb) quit

Appears that sincos is causing the problem.

History

#1 Updated by Paul 3 months ago

  • Status changed from New to In Progress

Agreed there is a problem. Try r17487.

#2 Updated by Marcelo 3 months ago

It is working again and cmake logs from r17362 and r17487 are the same.

#3 Updated by Paul 3 months ago

  • Status changed from In Progress to Closed
  • Target version set to Candidate for next bugfix release
  • % Done changed from 0 to 100

Fixed.

Also available in: Atom PDF