Hi!
> "Voytek" == Voytek Lapinski <[EMAIL PROTECTED]> writes:
Voytek> Ok... I've posted briefly regarding this, but heres a complete bug report.
Voytek> Yeah I know its kinda long, but I thought it better to include more rather
Voytek> than less.
Voytek> We are seeing a problem which res
hey,
i've been observing a similar kind of a problem
with mysql 3.23.32 on a Linux 2.4.2 kernel. The
backtrace that i'm getting is different, but even that
fails a sanity check. When i resolved the incomplete
backtrace, it showed me thread creation functions and
something of that sort. The
Gerald Clark wrote:
>
> Voytek Lapinski wrote:
> >
[...]
> I have been following the SIG 11 threads that have appeared lately.
> It seems to me all reporters have been running SMP kernels.
>
> What happens if you bring the machine up single CPU?
>
I am still getting occasional signal 11 crash
Voytek Lapinski wrote:
>
> Ok... I've posted briefly regarding this, but heres a complete bug report.
> Yeah I know its kinda long, but I thought it better to include more rather
> than less.
>
> We are seeing a problem which results in mysqld dying with a SIGSEGV. The
> problem has been confirm
>Ok... I've posted briefly regarding this, but heres a complete bug report.
>Yeah I know its kinda long, but I thought it better to include more rather
>than less.
>
>We are seeing a problem which results in mysqld dying with a SIGSEGV. The
>problem has been confirmed on both these machines
>
>L
Ok... I've posted briefly regarding this, but heres a complete bug report.
Yeah I know its kinda long, but I thought it better to include more rather
than less.
We are seeing a problem which results in mysqld dying with a SIGSEGV. The
problem has been confirmed on both these machines
Linux lin
