Any ideas on why db was doing what it was doing instead of allowing me
to get a backtrace?
Petr
Scott Ullrich wrote:
Petr Janda wrote:
[snip]
Why is this bug still not fixed? Ive just had 20 days uptime and this
is 2nd time it happened in 2 months. If there is a such thing as a
*gravely* bug, this is one.
It is incredibly difficult to locate these types of bugs without a
backtrace / coredump. Hopefully next time db> will be responsive and
you can either get a backtrace or call doadump to create a corefile.
Scott
