[PLUG] glibc/mysql dying

[Robby Russell]

help!

I had a program that needed a newer version of glibc to run...so I used a
rpm from mandrake to upgrade...and it kept complainign about
dependancies..so I eventually added --nodeps...

the program worked!
(good, right?)

well..now...mysqld dies upon startup. (seg fault?)

I see this in my .err file... but not sure where to look for more
information.

I can only assume that the glibc upgrade killed it...and now I don't know
what to do. I downloaded mysql to try to install it again..but that didn't
seem to work either. any suggestions?



--

021112 07:56:41  mysqld started
/usr/sbin/mysqld: ready for connections
021112 07:57:52  mysqld started
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked agaist is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail

key_buffer_size=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Bogus stack limit or frame pointer, fp=0xbfffe078,
stack_bottom=0x3bdbc910, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x3ac6fc20  is invalid pointer
thd->thread_id=1919639395

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 1919639395 did to cause the crash.  In some cases
of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
021112 07:57:52  mysqld ended