Bug #10286 mysqldump with complete insert crashes on long rows
Submitted: 1 May 2005 8:37 Modified: 19 May 2005 2:25
Reporter: Robert McKee
Status: Closed
Category:Client Severity:S2 (Serious)
Version:4.1.10a OS:Linux (CentOS 3.4)
Assigned to: Jim Winstead Target Version:

[1 May 2005 8:37] Robert McKee 
Description:
I have a large table with many columns (480), and long column names.  When doing a
mysqldump -c -uUser -pPassword, the database dump will stop right before the first insert
and say "Segmentation fault".  However, if I do not specify the -c, then it correctly
dumps the database.

How to repeat:
execute mysqldump -c on a database that contains a table with many (480+) columns that
have long column names.
[2 May 2005 12:27] Hartmut Holzgraefe 
verified, see attached testcase bug10286.sql

the first table included is still within limits, the second one with one additional
fields
makes mysqldump -c crash
[2 May 2005 12:27] Hartmut Holzgraefe 
test file that reproduces the crash

Attachment: bug10286.sql (application/octet-stream, text), 25.79 KiB.
[8 May 2005 21:01] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/24694
[19 May 2005 2:08] Jim Winstead 
Fixed in 4.1.13 and 5.0.6.
[19 May 2005 2:25] Paul DuBois 
Noted in 4.1.13, 5.0.6 changelogs.