[Nss-mysql-users] Cannot start mysql with nss-mysql installed

[Dan Slatford]

I played with nss-mysql on debian potato earlier in the year, and found
that when [re]starting the mysql server on the same machine running
nss-mysql, mysql would crap itself and die.

Now, several months later, on debain woody machine (and using mysql
binaries from mysql.com with nss-mysql 0.40 freshly compiled) -
everything works a treat - expect I still can't restart mysql with
nss-mysql enabled, which is something of a major worry.

This happens:

020816 11:57:30  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=16773120
record_buffer=131072
sort_buffer=524280
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 = 80379
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=0xbfffe898,
stack_bottom=0x1703cd90, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x1638c690  is invalid pointer
thd->thread_id=65537


Anybody have any ideas why this is?

Thanks,

-- 
dan.