For the record, what operating system and distribution
are you using? (Linux/Redhat, etc?)
I am wondering if segfaults occur on different systems.
(for example Redhat>7 being different than 7).
I am still curious as to why Ben Logan got his problem fixed by
CFLAGS=-g ./configure on Redhat 8.0.
ref:GRASSLIST:2164,2180
John
-----Original Message-----
From: Carl Brown [mailto:cbsled@ncia.net]
Sent: Thursday, January 22, 2004 9:31 AM
To: grasslist@baylor.edu
Subject: [GRASSLIST:2328] Re: r.in.gdal : Unresolvable problems? --
Solved
On Wednesday 21 January 2004 15:25, Paul Kelly wrote:
> Hello
> I'm not sure what your exact problem was here but I spent some time
> investigating the r.in.gdal segmentation fault problem a
few months ago
I had the dreaded segfault problem. It had occurred on this
particular system
since GRASS was first installed many moons ago. It is now fixed!!!
Thanks, Paul!
What I did, step by step:
CVS update both GRASS and gdal to:
GRASS 5.0.3
gdal 1.1.9
$ find /usr/local -name *gdal*
Delete all relevant results.
$ find /usr/local -name *ogr*
Delete all relevant results.
$ cd {gdal source directory}
$ make clean
$ ./configure --without-grass
$ make
$ su
# make install
# exit
$ cd {grass source directory}
$ make clean
$ ./configure --with-gdal
$ make
$ su
# make install
# exit
--
Carl Brown
Whitefield, NH USA
-----
John Gillette wrote:
For the record, what operating system and distribution
are you using? (Linux/Redhat, etc?)
I am wondering if segfaults occur on different systems.
(for example Redhat>7 being different than 7).
I am still curious as to why Ben Logan got his problem fixed by
CFLAGS=-g ./configure on Redhat 8.0.
There are three main reasons why bugs often "vanish" when disabling
optimisation:
1. It's a compiler bug which only applies when optimising (in my
experience, *most* compiler bugs only apply when optimising).
2. It's an aliasing bug in the code (which only matters when
optimising).
3. Optimisation tends to make stack frames smaller (as some local
variables can often be eliminated), increasing the likelyhood that a
buffer overrun will trash something important.
As compilers optimise more aggresively, bugs which vanish when
optimisation is disabled are likely to become more common. This is a
substantial nuisance, as you often need to disable optimisation in
order to realistically use a debugger.
--
Glynn Clements <glynn.clements@virgin.net>
On Thursday 22 January 2004 07:54, John Gillette wrote:
For the record, what operating system and distribution
are you using? (Linux/Redhat, etc?)
I am wondering if segfaults occur on different systems.
(for example Redhat>7 being different than 7).
I am still curious as to why Ben Logan got his problem fixed by
CFLAGS=-g ./configure on Redhat 8.0.
ref:GRASSLIST:2164,2180
John
Just to help document this, Ben's solution worked for my system as well. I am
running Grass5.3 on a suse 9.0 system. The hardware is 1 gb of ram, 120 gb
hd, AthlonXP, and nvidia geforce4 Ti 4400 graphics card.
John Dougherty