mysqld 4.1 immediatelly crashes after connect()

[Dorin H]

Hi there,
  I resubmit this question to ports list, maybe
somebody informed may have an opinion about it. 
Please cc me as I am not subscribed to ports
discussion list.
  Does anyone have a functional 4.1 mysql server?
There is a PR related to 4.0 version of the server,
but I see the server crashing since updating it to 4.1
(sometime in feb.).  It could be related to the kse,
since it started crushing immediately after building
world to use new threading. All ports are rebuilt, no
dep on libc_r as I can see.

  The mysql client connects ok.  But any type of
socket based connection produces a sig 11. This
happens deterministic at the moment of connect(). No
luck from the kse update.  Building mysqld in debug
version does not provide any additional information in
traces/logs. Dbg seems to have problem running a kse
threaded app (it hangs ?).
  Any info on subject, suggestions, ideas, comments,
please?  
TIA,
/Dorin.

Info:
%uname -v
FreeBSD 5.2-CURRENT 

%/usr/local/libexec/mysqld -V
/usr/local/libexec/mysqld  Ver 4.1.1-alpha for
portbld-freebsd5.2 on i386 (FreeBSD port:
mysql-server-4.1.1_2)

%mysql -V
mysql  Ver 14.3 Distrib 4.1.1-alpha, for
portbld-freebsd5.2 (i386)

Here is the trace (in case somebody can see more):
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  gettimeofday(0xbfa98f70,0)
 45887 mysqld   RET   gettimeofday 0
 45887 mysqld   CALL  kse_release(0x8414fa4)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  gettimeofday(0xbfa98f70,0)
 45887 mysqld   RET   gettimeofday 0
 45887 mysqld   CALL  kse_release(0x8414fa4)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  fcntl(0x3,0x4,0x6)
 45887 mysqld   RET   fcntl 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL 
accept(0x3,0xbfbfe9b0,0xbfbfe66c)

<<< Here came the connect...

 45887 mysqld   RET   accept 8
 45887 mysqld   CALL  fcntl(0x3,0x4,0x2)
 45887 mysqld   RET   fcntl 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  sigaction(0x14,0xbfbfe5a0,0)
 45887 mysqld   RET   sigaction 0

<<  No the segv signal :(

 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  getpid
 45887 mysqld   RET   getpid 45887/0xb33f
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  sigaction(0xb,0xbfbfddb0,0)
 45887 mysqld   RET   sigaction 0
 45887 mysqld   CALL  sigaction(0xb,0,0x2843fd10)
 45887 mysqld   RET   sigaction 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   RET   fork 0
 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  write(0x2,0xbfbfd650,0xf8)
 45887 mysqld   RET   write 248/0xf8
<snip>
>> Here it displays the error message in
/var/db/mysql/host.err


 45887 mysqld   CALL  kse_release(0x8414f9c)
 45887 mysqld   RET   kse_release 0
 45887 mysqld   CALL  exit(0x1)




__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com