Bug #19973 Mysqld crash
Submitted: 20 May 2006 20:18 Modified: 20 May 2006 20:45
Reporter: Sascha Schauf Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:20.05.2006 OS:Linux (Debian Sarge)
Assigned to: CPU Architecture:Any

[20 May 2006 20:18] Sascha Schauf 
Description:
dev0:~# resolve_stack_dump -s /tmp/mysqld.sym -n /root/mysqld.stack
0x810e48b handle_segfault + 667
0xffffe420 _end + -138589800
0xb7d24bb4 _end + -1349537492
0xb7d22f96 _end + -1349544690
0xb7d231d5 _end + -1349544115
0xb7e105dc _end + -1348572332
0xb7e10469 _end + -1348572703
0x8111b38 _Z9set_portsv + 104
0x8111bab _Z11server_initv + 27
0x810ef13 main + 1539
0xb7d3beb0 _end + -1349442520
0x80bf671 _start + 33

Don`t know what about this bug =(

How to repeat:
Don`t know what to write in here, hope to get some help to fix the bug.
[20 May 2006 20:45] Hartmut Holzgraefe 
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.
[20 May 2006 20:46] Hartmut Holzgraefe 
Could you provide a core dump?