Robert,

I found this web site: http://web.mit.edu/answers/c/unix_bus_or_seg.html

and the skinny of the page is:

<snip>
If the program displays this message:

        Bus error
or
        Segmentation fault

... then the program was trying to access a memory location outside its
address space.  The computer detected this problem and sent a signal to your
program, which caused it to abort.

Things that cause bus errors and segmentation violations are typically
out-of-bounds array references and/or references through uninitialized or
mangled pointers...
</snip>

I'll take a look to see where we may be going 'out of bounds'.  Maybe you
can change one parameter at a time to see if that makes a difference in a
run that works and one that ends that the bus stop.

Mark
> -----Original Message-----
> Now here's the BUT - just tried it with one of our biggest
> reports and got a
> 'Bus error'. I've only listed the variables that changed
> during this run.
> Anybody know what is causing this and how to fix it? We will
> save forests
> not just trees if it can be made to work.
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *