[OOPS] "Random" segmentation fault

[Neilson Henriques]

First it would like to ask for if please could have a
reply in English therefore I would like very much to learn Russian
but my time is scarce. :-(
My problem is that Oops leaves due to a Segmentation fault generating
a "core" file. I following the use of memory and processor and both is
free most of the time. During 2 consecutive months Oops did not
present any problem but since 1 week it started to give these errors
that I spoke.
Already I also changed of version migrating the 1.4.6 (with DB 2.7.7)
to 1.4.10 (experimental) with DB 2.7.7 having made tests with 1.4.6/DB 3.0.55
and 1.4.10/DB 3.0.55 getting the same results unhappyly. The used
configuration file (.cfg) is the standard done modifications only in
sessions "storage" and "DB". The system that always I used with Oops is the
Solaris 8/Intel and GNU GCC 2.95.2 (according to Igor's opinion). To eliminate
the probability of a hardware problem, I changed of machine, I
reinstalled Solaris 8 and the Oops continue to exit. Does anybody had the same
experience or at least it knows as to help me?

I'm thankful by any attention and helps.

Greats for Igor and Oops programmers, it rocks !

Hugs,

Neilson Henriques


=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
Archive is accessible on http://www.paco.net/oops/