It would be helpful if you included more information, such
as exactly which version of the ht://Dig package you
installed (see http://www.htdig.org/FAQ.html#q5.33\), and
exactly which of the programs in the suite is giving you the
bus error.
Also, it would be very useful if you could send us a stack
backtrace from the core dump, or from the program running
under the debugger. See the last paragraph of FAQ question
5.14 (http://www.htdig.org/FAQ.html#q5.14). If you don't
have gdb on your Solaris system, could you try getting a
backtrace using whichever debugger you have on your system?
Without a backtrace, we wouldn't be able to even begin
tracking this down.
Finally, if you're not running the latest release (3.1.6 for
the 3.1.x stable series, or 3.2.0b6 for the 3.2 beta
series), please try installing the latest to see if the
problem still occurs. Also, if you're running 3.1.6, try
skimming through the patch archive at
ftp://ftp.ccsf.org/htdig-patches/3.1.6/ to see if there are
any fixes which might help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=149687
It would be helpful if you included more information, such
as exactly which version of the ht://Dig package you
installed (see http://www.htdig.org/FAQ.html#q5.33\), and
exactly which of the programs in the suite is giving you the
bus error.
Also, it would be very useful if you could send us a stack
backtrace from the core dump, or from the program running
under the debugger. See the last paragraph of FAQ question
5.14 (http://www.htdig.org/FAQ.html#q5.14). If you don't
have gdb on your Solaris system, could you try getting a
backtrace using whichever debugger you have on your system?
Without a backtrace, we wouldn't be able to even begin
tracking this down.
Finally, if you're not running the latest release (3.1.6 for
the 3.1.x stable series, or 3.2.0b6 for the 3.2 beta
series), please try installing the latest to see if the
problem still occurs. Also, if you're running 3.1.6, try
skimming through the patch archive at
ftp://ftp.ccsf.org/htdig-patches/3.1.6/ to see if there are
any fixes which might help.