Bug #33071 Stack Smashing and MySQL Termination
Submitted: 7 Dec 2007 19:19 Modified: 29 Feb 2008 12:15
Reporter: Dan F Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: General Severity:S2 (Serious)
Version:5.0.22 OS:Linux (Red Hat Linux Server 5.1)
Assigned to: CPU Architecture:Any
Tags: Stack smashing

[7 Dec 2007 19:19] Dan F
Description:
When I run long insert or update queries (e.g., runtime of more than a day), often I get an error that says "stack smashing detected ... mysql terminated". (Below is an example).

Does anyone know what this means and how to fix it? Also, should I not trust the results of the query? It seems to finish correctly (i.e. the mysql termination comes after the query finishes), but I'm not 100% sure.

Thanks for any insights into this,
Dan

EXAMPLE:

mysql> UPDATE table1, table2
-> SET table1.fieldx = table2.fieldy
-> WHERE table1.fieldz=table2.fieldz;
Query OK, 49500642 rows affected (1 day 15 hours 37 min 28.32 sec)
Rows matched: 49500642 Changed: 49500642 Warnings: 0

*** stack smashing detected ***: mysql terminated
Aborted

How to repeat:
The query is given above. Please let me know what other information would be useful. I'm not a developer and so don't know what's needed here. (I posted this is in the Newbie MySQL forums, and two people told me to submit it as a bug release.)
[8 Dec 2007 20:20] Sveta Smirnova
Thank you for the report.

But version 5.0.22 is quite old. Please upgrade to current version 5.0.51, try with it and inform us about results.
[10 Dec 2007 14:57] Susanne Ebrecht
Also it would be interesting, which storage engine you use.
[9 Jan 2008 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[31 Jan 2008 12:15] Susanne Ebrecht
Dan,

we still need the feedback, if all would work fine with MySQL 5.0.51.
[1 Mar 2008 0:01] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".