[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults i
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave |
Date: |
Tue, 29 Mar 2016 00:19:43 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #55, bug #47372 (project octave):
I tested the example on Stack Overflow and it does segfault for me, but not
reliably; Sometimes it works, sometimes it doesn't.
When I use ldd on the created main binary I see that libgomp is still not
included. On the other hand, if I disable the linker's automatic pruning of
unused libraries it does work. I only want to disable pruning for this one
particular library so I used
setenv LDFLAGS -Wl,--no-as-needed,-lgomp,--as-needed
This fixes things in the test program.
I went back and added the same stanza to the extra LDFLAGS in configure.ac and
now it works! There is no segfault and ldd reports that libgomp is linked in.
This obviously is a GCC version/OS dependent issue. For the moment, I force
GCC to link in libgomp if OpenMP is enabled. See cset
http://hg.savannah.gnu.org/hgweb/octave/rev/f80b46f7d3d8.
The WARN_LDFLAGS variable does not exist on the stable branch so if we want to
backport this to the stable branch it will need a different strategy.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47372>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, (continued)
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Rik, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Rik, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Mike Miller, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Rik, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Rik, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave,
Rik <=
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Mike Miller, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Mike Miller, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/28
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Mike Miller, 2016/03/29
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Rik, 2016/03/29
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, John W. Eaton, 2016/03/30
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Rik, 2016/03/30
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Rik, 2016/03/30
- [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave, Hartmut, 2016/03/30