Bug #27227 Solaris 10 Sparc coredump on either Yassl or openssl
Submitted: 16 Mar 2007 21:14 Modified: 11 Apr 2007 12:56
Reporter: Spicy Spam Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Tests Severity:S7 (Test Cases)
Version:5.0.37 OS:Solaris (Solaris 10 Sparc )
Assigned to: Magnus Blåudd CPU Architecture:Any

[16 Mar 2007 21:14] Spicy Spam
Description:
If Yassl or Openssl is enabled in the config, the resulting build will fail all SSL related test, such as client_xml mysqldump ssl ssl openmssl_1 ssl_compress ssl_connect ssl_des.

The cliemt_xml caused by is caused by mysqldump which core dump during the test. A quick glance at the core, I get:

> ::status
debugging core file of mysqldump (32-bit) from labbox
file: /tmp/sum/mysql-5.0.37/client/.libs/mysqldump
initial argv:
/tmp/sum/mysql-5.0.37/client/.libs/mysqldump --no-defaults -uroot --port=9306 -
threading model: multi-threaded
status: process terminated by SIGBUS (Bus Error)

> ::stackregs
ffbfe188 libmysqlclient.so.15.0.0`mysql_options+0x124(319d0, 15, 31942, 31800, 1, 31800)
  %l0-%l3:        0        0        0        0
  %l4-%l7:        0        0        0 ff33d92c
  main+0x5a4:
  call      +0x15674      <PLT=libmysqlclient.so.15.0.0`mysql_options>

ffbfe200 main+0x5a4(32018, 0, 31800, 32000, 31c00, 31800)
  %l0-%l3:    31800        0 ffbfea9d    33150
  %l4-%l7:    31800 ffbfe884    31c00    31c00
  _start+0x5c:             call      +0x8b04       <main>

ffbfe840 _start+0x5c(0, 0, 0, 0, 0, 0)
  %l0-%l3:        9 ffbfe8a4        0        0
  %l4-%l7:        0        0        0        0

> ::regs
%g0 = 0x00000000                 %l0 = 0x00000000
%g1 = 0xfffffe94                 %l1 = 0x00000000
%g2 = 0x00000000                 %l2 = 0x00000000
%g3 = 0x00000000                 %l3 = 0x00000000
%g4 = 0x00000000                 %l4 = 0x00000000
%g5 = 0x00000000                 %l5 = 0x00000000
%g6 = 0x00000000                 %l6 = 0x00000000
%g7 = 0xff252000                 %l7 = 0xff33d92c
%o0 = 0x00061b90                 %i0 = 0x000319d0 mysqldump`mysql_connection
%o1 = 0x00061800                 %i1 = 0x00000015
%o2 = 0x00000000                 %i2 = 0x00031942
mysqldump`opt_ssl_verify_server_cert
%o3 = 0x00000000                 %i3 = 0x00031800
mysqldump`my_long_options+0x1498
%o4 = 0xff2dbd9c libmysqlclient.so.15.0.0`mysql_options+0x284 %i4 = 0x00000001
%o5 = 0x00000054                 %i5 = 0x00031800
mysqldump`my_long_options+0x1498
%o6 = 0xffbfe188                 %i6 = 0xffbfe200
%o7 = 0xff2dbb20 libmysqlclient.so.15.0.0`mysql_options+8 %i7 = 0x0001aaa8
main+0x5a4

 %psr = 0xfe000004 impl=0xf ver=0xe icc=nzvc
                   ec=0 ef=0 pil=0 s=0 ps=0 et=0 cwp=0x4
   %y = 0x00000000
  %pc = 0xff2dbc3c libmysqlclient.so.15.0.0`mysql_options+0x124
 %npc = 0xff2dbc40 libmysqlclient.so.15.0.0`mysql_options+0x128
  %sp = 0xffbfe188
  %fp = 0xffbfe200

 %wim = 0x00000000
 %tbr = 0x00000000

The platform is Solaris 10 sparc Generic_118833-36 sun4u, fully patched. In comparison, the Solaris 10 x86 build with Yassl passes all the tests.

Thanks,

-- Sum

How to repeat:
build on solaris 10 with "--with-yassl" using gcc 3.4.6.
[30 Mar 2007 12:37] Sveta Smirnova
Thank you for the report.

Verified as described with community tree.
[11 Apr 2007 12:56] Magnus Blåudd
Duplicate of Bug #24121  Incorrect test for SSL_VERIFY_SERVER_CERT