Bug 623475

Summary: [abrt] crash in mysql-5.1.48-2.fc13: ____strtoul_l_internal: Process /usr/bin/mysql was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Damien Grassart <damien>
Component: mysqlAssignee: Tom Lane <tgl>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: hhorak, tgl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: abrt_hash:0f145aa893d6666da0ac8f4343fcfa54955ad14d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-12 01:28:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Damien Grassart 2010-08-11 21:21:04 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: mysql -h oltp -u admin -px xxxxxxx
component: mysql
crash_function: ____strtoul_l_internal
executable: /usr/bin/mysql
global_uuid: 0f145aa893d6666da0ac8f4343fcfa54955ad14d
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: mysql-5.1.48-2.fc13
rating: 4
reason: Process /usr/bin/mysql was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

comment
-----
Tried to describe a table on a MySQL server that "has gone away" and hit control-C while it was trying to reconnect:

> desc zip_code;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
^CSegmentation fault (core dumped)

Comment 1 Damien Grassart 2010-08-11 21:21:06 UTC
Created attachment 438299 [details]
File: backtrace

Comment 2 Tom Lane 2010-08-12 01:28:00 UTC
I didn't have any luck reproducing this --- the problem probably only occurs if you manage to hit control-C during a very narrow window.  It doesn't seem important enough to justify carrying our own patch, but I've filed the problem upstream at http://bugs.mysql.com/bug.php?id=55932

Comment 3 Tom Lane 2010-08-15 15:27:29 UTC
Upstream is wondering whether the mysql server you were connecting to is also current-version.

Comment 4 Damien Grassart 2010-08-15 17:13:54 UTC
The server is an older version: 4.1.25-pro-gpl-log. I've also posted this on the upstream issue.