[GRASS5] Bus errors

GRASS GIS GRASS GIS developer
1

Anyone have a suggestion as to what might be causing a 'Bus error' message in a number of commands? I havee finished building 51 from cvs today on OS X 10.3.6. My first try was with shared libraries, but I was still getting the db_open_database() not implemented with dbf, so I tried building with the config option --disable-shared (per Hamish's suggestion... and that seemed to make a difference).

Now v.in.dwg seems to be working fine:

GRASS 5.7.cvs:~ > v.in.dwg in=cc1.dxf out=cc1
WARNING: The vector 'cc1' already exists and will be overwritten.
WARNING: Table 'cc1' linked to vector did not exist.
11276 elements processed
Building topology ...
11276 primitives registered
0 areas built 8%
0 isles built
Topology was built.
Number of nodes : 11440
Number of primitives: 11276
Number of points : 3539
Number of lines : 7657
Number of boundaries: 0
Number of centroids : 0
Number of faces : 80
Number of areas : 0
Number of isles : 0
GRASS 5.7.cvs:~ > g.list vect
Bus error
GRASS 5.7.cvs:~ >

But I'm this odd Bus error. I've seen it with g.list, g.copy, and g.remove. Perhaps there are others. Any suggestions as to how to start diagnosing this problem would be apprecieated

Kirk R. Wythers
Dept. of Forest Resources
University of Minnesota
email: kwythers@umn.edu
tel: 612.625.2261
fax: 612.625.5212

2

Kirk R. Wythers wrote:

GRASS 5.7.cvs:~ > g.list vect
Bus error
GRASS 5.7.cvs:~ >

But I'm this odd Bus error. I've seen it with g.list, g.copy, and
g.remove. Perhaps there are others. Any suggestions as to how to start
diagnosing this problem would be apprecieated

My first guess is that something is performing a non-aligned memory
access (e.g. reading an int from an odd-numbered memory address).

This works on x86, on most other platforms it will generate an
exception (which usually corresponds to SIGBUS on Linux), and on the
ARM processors (at least, on ARM2 and ARM3; I don't know about the
more recent ones) it will result in garbage data.

The simplest way to locate the fault is likely to be to run the
program in question under a debugger, e.g.

  $ gdb $GISBASE/bin/g.list
  > run vect
  <error message regarding SIGBUS>
  > where

--
Glynn Clements <glynn@gclements.plus.com>