>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 lindt 2.2.18 #2 SMP Mon Feb 26 15:23:32 EST 2001 i686 unknown
>Dell PowerEdge 4300 - Dual Pentium 3-500 - 1Gb RAM, 1.6Gb swap
>
>Linux lisa 2.4.1 #7 SMP Fri Feb 16 15:21:45 EST 2001 i686 unknown
>IBM Rackmount Server 325 - Dual Pentium Pro-200 - 512Mb RAM, 1Gb Swap
>
>And using mysqld versions 3.23.32,3.23.33 and 3.23.35. To confirm that the
>problem isn't related to libraries, compilers or configuration specific to our
>build environment, I have also tested the standard linux-i386 binary distro of
>3.23.35, and the problem also exists there.
I tested your case on my test machine (Redhat 6.2 with latest patches):
Linux krusty 2.2.16-4.lfs #1 Wed Jul 12 14:08:46 EDT 2000 i686 unknown
IBM P-Pro 200 256MB 128MB Swap
Using a self compiled RPM of MySQL 3.23.35 - no problems here. How long must I run
before the problem manifests itself? 30mins ok? It is still running though.
I see both your machines are SMP. Try to boot with a UNI Processor kernel and see
again. There have been problems in the past with SMP installations.
--
Richard Ellerbrock
[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
