At 06:20 PM 08/12/02 -0400, Thomas M. Parris wrote:
>> Then it's off to gdb land and fetch a back trace after the
>> segfault and try
>> and see what's blowing up.
>
>--> I was afraid you would say that.  I think I'll see if I get the same
>problem on a more recent version of Solaris.  If not, I'll just have to wait
>for our new machine to come on line.

I guess it would be nice to see where the segfault is happening (i.e. in
swish or in some of the library code).  It's easy to get a back trace:

  $ cd swish-e/src
  $ gdb swish-e
  run -e -i /h/www/religion/forebib
  <segfault>
  bt


-- 
Bill Moseley
mailto:moseley@hank.org