Hi strk
I think you are right, after testing I noticed that GEOS compiles with
-O2 by default. If you change CFLAGS/CXXFLAGS to be -O1 instead this
SIGABRT does not seem to happen. Is this a bug that can or should be
filed with the gcc project?
Thanks!
On 09/01/2010 03:37 AM, strk wrote:
Hi,
No I'm using SVN trunk. But going back a 100 revisions or so the problem
is the same. I haven't tried it with the stable release but I imagine
the problem is the same.
On 09/22/2010 08:35 AM, strk wrote:
On Wed, Sep 22, 2010 at 08:12:39AM -0400, Alex Trofast wrote:
Hi strk
I think
On Wed, Sep 22, 2010 at 12:13:51PM -0400, Alex Trofast wrote:
On 09/22/2010 08:35 AM, strk wrote:
On Wed, Sep 22, 2010 at 08:12:39AM -0400, Alex Trofast wrote:
I think you are right, after testing I noticed that GEOS compiles with
-O2 by default. If you change CFLAGS/CXXFLAGS to be -O1
On Tue, Aug 31, 2010 at 08:26:29PM -0400, Alex Trofast wrote:
Greetings all, I'm getting a SIGABRT in GEOS, but not on all Linux distros.
The following is a partial backtrace from Ingres:
#2 0x0030e4a2b7b5 in __assert_fail () from /lib64/libc.so.6
#3 0x7fa6f3ea2623 in
